dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-3425

HIGH · 7.3 CVSS v4.0 Published 2025-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
76/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The IntelliSpace portal application utilizes .NET Remoting for its functionality. The vulnerability arises from the exploitation of port 755 through the deserialization vulnerability. After analyzing the configuration files, we observed that the server had set the TypeFilterLevel to Full which is dangerous as it can potentially lead to remote code execution using deserialization. This issue affects IntelliSpace Portal: 12 and prior.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IntelliSpace Portal uses .NET Remoting on port 755 with TypeFilterLevel set to Full, which allows deserialization of arbitrary types and can lead to remote code execution.

MitigationSet TypeFilterLevel to Low in the .NET Remoting configuration, or disable .NET Remoting if not required, and restrict network access to port 755.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
High
Privileges
None
Authentication
Y
User interaction
A
Scope
P

CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:Y/R:U/V:C/RE:M/U:Green

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if IntelliSpace Portal is installed
    Check system for presence of IntelliSpace Portal software - look for installation directory, registry entries, or installed programs listing
    Affected if IntelliSpace Portal is found on the system
  2. Verify if port 755 is listening
    Run netstat -an | findstr 755 or similar network scan on port 755 to detect if .NET Remoting service is active
    Affected if Port 755 is open and accepting connections
  3. Locate the .NET Remoting configuration file
    Find the application configuration file (typically app.config or isap.config) in the IntelliSpace Portal installation directory that defines the .NET Remoting endpoint
    Affected if Configuration file exists and defines a remoting endpoint on port 755
  4. Check TypeFilterLevel setting
    Open the remoting configuration file and search for TypeFilterLevel attribute in the <serverTimeout> or <channel> element
    Affected if TypeFilterLevel is set to Full (not Low)
  5. Assess network exposure
    Determine if port 755 is accessible from network addresses other than localhost - check firewall rules and binding addresses
    Affected if Port 755 is accessible from non-localhost addresses

Environment is affected if IntelliSpace Portal is installed with .NET Remoting enabled on port 755 and TypeFilterLevel is set to Full, especially if exposed to network access

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Set TypeFilterLevel to Low in the .NET Remoting configuration, or disable .NET Remoting if not required, and restrict network access to port 755.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3425 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3425 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data