CVE-2025-2229 Philips Intellispace Cardiovascular (ISCV) Use of Weak Credentials
High 8.5
Published
Updated
Check this codebase for CVE-2025-2229 and fix it if it is affected.
What it is: CVE-2025-2229 is a high-severity vulnerability in Philips Intellispace Cardiovascular (ISCV), published on 13 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2229 in the wild and no public exploit code.
Affected product: Philips Intellispace Cardiovascular (ISCV). No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2025-2229/ (Markdown: https://insights.sbomify.com/CVE-2025-2229/index.md)
Attackers can bypass authentication in Philips ISCV by exploiting a hardcoded AES key used to generate access tokens.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-2229?
CVE-2025-2229 is a high-severity vulnerability in Philips Intellispace Cardiovascular (ISCV), published on 13 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
A token is created using the username, current date/time, and a fixed AES-128 encryption key, which is the same across all installations.
Weakness: CWE-1391
Which versions are affected by CVE-2025-2229?
How do I fix CVE-2025-2229?
No fix has been published for CVE-2025-2229 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-2229 being exploited?
There is no known exploitation of CVE-2025-2229 in the wild and no public exploit code.
Sources
Also known as GHSA-x7gm-m6fc-fx8q.