CVE-2025-15679
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:P/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:N/R:U/V:C/RE:L/U:ClearCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2025-15679 is a high-severity Empty Password in Configuration File (CWE-258) vulnerability in Site (inferred from references). Its CVSS base score is 7.3 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 1th 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 AC-3 (Access Enforcement) and IA-2 (Identification and Authentication (Organizational Users)) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-210890
Vulnerability Data
Under certain circumstances such as reset to factory default operation, the BMC root account is made active without a password on BullSequana XH3406 and XH3515.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 3 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement applies approved authorizations and therefore rejects attempts that rely on missing or empty credentials.
Mandatory identification and authentication of users cannot be satisfied by an empty password, blocking unauthenticated access paths.
Authenticator management requires verification and secure distribution of passwords, directly stopping empty values from being accepted in configuration.
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.
Password-strength policy enforcement directly blocks empty passwords while authentication covers far more than credential storage.
Hardened configuration baselines and reviews prevent empty-password settings, yet configuration management addresses many other settings beyond credentials.
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.
Requires secure handling and protection of authentication credentials, directly addressing empty passwords in config files.
Secure development lifecycle includes controls that should prevent shipping empty passwords in configuration artifacts.
Secure coding standards explicitly forbid hard-coded or empty credentials.
Mandates secure authentication mechanisms, preventing use of empty or weak passwords.
Configuration management processes would normally detect and correct insecure empty-password settings.
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` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (2 rules)
- V-248715 OL 8 must not allow blank or null passwords in the system-auth file. prevents CWE-258
- V-248716 OL 8 must not allow blank or null passwords in the password-auth file. prevents CWE-258
Oracle Linux 9 (2 rules)
- V-271634 OL 9 must not allow blank or null passwords. prevents CWE-258
- V-271706 OL 9 SSHD must not allow blank passwords. prevents CWE-258
RHEL 7 (2 rules)
- V-204424 The Red Hat Enterprise Linux operating system must not allow accounts configured with blank or null passwords. prevents CWE-258
- V-204425 The Red Hat Enterprise Linux operating system must be configured so that the SSH daemon does not allow authentication using an empty password. prevents CWE-258