Patient-record access via AuthContext token replay
Published Mar 13, 2025 · Updated Mar 17, 2025
Authentication bypass in Philips IntelliSpace Cardiovascular 5.1 and earlier allows local users to read patient records via AuthContext token replay. The Windows login flow accepts a previously issued AuthContext token again instead of binding it to a single authenticated session. Exploitation requires local access and a reusable token for a logged-in ISCV user, after which the attacker assumes that user's session and patient-record access.
Summary
What happened
Authentication bypass in Philips IntelliSpace Cardiovascular 5.1 and earlier allows local users to read patient records via AuthContext token replay. The Windows login flow accepts a previously issued AuthContext token again instead of binding it to a single authenticated session. Exploitation requires local access and a reusable token for a logged-in ISCV user, after which the attacker assumes that user's session and patient-record access.
The record
- CVE
- CVE-2025-2230
- Published
- Mar 13, 2025
- Updated
- Mar 17, 2025
- Vendor
- Philips
- Product
- Philips IntelliSpace Cardiovascular
- Classifications
- CWE-287, T1550.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 13, 2025CVE publishedPublication date reported by the CVE source.
- Mar 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=5.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo