dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-3424

HIGH · 7.7 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 →
82/100
Remediation priority · High
No privileges Zero-click

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 "Object Marshalling" technique, which allows an attacker to read internal files without any authentication. This is possible by crafting specific .NET Remoting URLs derived from information enumerated in the client-side configuration files. 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

A path traversal/unauthenticated file read vulnerability in Philips IntelliSpace Portal allows remote attackers to access internal files via crafted .NET Remoting URLs on port 755 using the Object Marshalling technique. The attack leverages information enumerable from client-side configuration files, enabling unauthenticated access without any credentials.

MitigationIf .NET Remoting is not essential for portal functionality, disable or block port 755 at the network perimeter. Otherwise, apply vendor patches when available and restrict network access to the affected port.

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
None
Scope
P

CVSS:4.0/AV:A/AC:H/AT:N/PR:N/UI:N/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. Confirm Philips IntelliSpace Portal installation
    Check system for presence of Philips IntelliSpace Portal software and note the installed version
    Affected if The software is installed and the version falls within the affected range (if known) or is an unpatched version
  2. Verify port 755 is listening
    Run 'netstat -an | grep 755' or 'ss -tlnp | grep 755' to check if the .NET Remoting port is open and bound to a service
    Affected if Port 755 is open and accepting connections, indicating .NET Remoting is enabled
  3. Check .NET Remoting configuration
    Inspect the IntelliSpace Portal configuration files for .NET Remoting endpoint definitions (look for 'TcpChannel' or 'RemotingConfiguration' in config files)
    Affected if .NET Remoting is configured and exposed on port 755
  4. Assess network exposure of port 755
    Review firewall rules or network perimeter configurations to determine if port 755 is accessible from untrusted networks
    Affected if Port 755 is accessible from external or untrusted network segments without filtering
  5. Review client-accessible configuration files
    Examine any configuration files accessible via the web interface or shared directories for .NET Remoting endpoint information
    Affected if Configuration files expose .NET Remoting service details that could enable the Object Marshalling attack vector

A user is affected if Philips IntelliSpace Portal is installed with .NET Remoting enabled on port 755 and that port is network-accessible, allowing unauthenticated path traversal via crafted remoting URLs.

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

If .NET Remoting is not essential for portal functionality, disable or block port 755 at the network perimeter. Otherwise, apply vendor patches when available and restrict network access to the affected port.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3424 — 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-3424 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