CVE-2025-2229
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/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:X/AU:X/R:X/V:X/RE:X/U:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-2229 is a high-severity Use of Weak Credentials (CWE-1391) vulnerability in Cisa (inferred from references). Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Default Accounts (T1078.001); ranked at the 2th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-2229, published on 2025-03-13, involves a vulnerability in token creation where the token is generated using the username, current date/time, and a fixed AES-128 encryption key that remains the same across all installations. This flaw, classified under CWE-1391, carries a CVSS v3.1 base score of 7.7 (AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N). It affects components referenced in CISA's ICS medical advisory ICSMA-25-072-01 and Philips security advisories.
Local attackers can exploit this vulnerability with low attack complexity and no privileges or user interaction required. Exploitation enables high-impact confidentiality and integrity violations, such as unauthorized access to sensitive information or token manipulation to impersonate users.
Mitigation details are provided in the referenced advisories, including https://www.cisa.gov/news-events/ics-medical-advisories/icsma-25-072-01 and https://www.philips.com/a-w/security/security-advisories.html.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6389
Vulnerability Data
A token is created using the username, current date/time, and a fixed AES-128 encryption key, which is the same across all installations.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 7 hardening rules · 3 OS baselines
V6.2.2V6.3.1V6.3.2V6.4.2
Mitigating Controls (NIST 800-53 r5) AI
IA-5 directly requires management of authenticator strength, distribution, and replacement, stopping default or guessable credentials from being introduced or used.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.AA-01's credential issuance and key-management processes directly block most weak/default credential usage, yet leave hard-coded or product-design instances of CWE-1391 only partially addressed.
Password-strength policies in PR.AA-03 directly block weak authenticators, but the control leaves hard-coded/default credentials largely unaddressed.
Hardened baselines and default-setting reviews directly block default/hard-coded creds (mostly), yet leave algorithmic guessing, reuse, and non-config sources of weak credentials untouched (partial).
Training raises password-hygiene awareness and can therefore reduce some weak-credential mistakes, yet supplies no enforcement mechanism and leaves the dominant technical sources of CWE-1391 untouched.
Role-based awareness training can reduce the chance developers or admins introduce weak credentials but supplies no enforcement or verification, leaving the bulk of CWE-1391 risk untouched.
Maintenance/patching can incidentally remove known weak-default creds in updated versions (partial forward) but does nothing to ensure credentials are strong at design, deployment or config time (none reverse).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Directly requires secure generation, distribution and storage of authentication credentials, eliminating default/hard-coded weak passwords.
Mandates secure authentication mechanisms that preclude use of weak or default credentials.
Secure-coding rules can prohibit hard-coded passwords, yet coverage depends on specific coding standards adopted.
Security testing can discover weak credentials, but does not guarantee they are prevented by design.
Enforces secure baseline configurations that should remove default credentials, yet does not guarantee credential strength.
Restricts privileged accounts but does not explicitly address default or hard-coded credentials for those accounts.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (3 rules)
- V-248667 OL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. prevents CWE-1391
- V-248668 OL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/password-auth file. prevents CWE-1391
- V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-1391
RHEL 7 (1 rule)
- V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. prevents CWE-1391
RHEL 8 (1 rule)
- V-244533 RHEL 8 must configure the use of the pam_faillock.so module in the /etc/pam.d/system-auth file. prevents CWE-1391