CVE-2025-42888
Raw vector
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:H/I:N/A:NSummary
CVE-2025-42888 is a medium-severity Cleartext Storage of Sensitive Information in Memory (CWE-316) vulnerability in Sap (inferred from references). Its CVSS base score is 5.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); 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 SC-39 (Process Isolation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-60990
Vulnerability Data
SAP GUI for Windows may allow a highly privileged user on the affected client PC to locally access sensitive information stored in process memory during runtime.This vulnerability has a high impact on confidentiality, with no impact on integrity and availability.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 3 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement limits which subjects can read memory locations holding the cleartext data.
Process isolation confines the cleartext data to its own execution domain, shrinking exposure.
Prevents unintended transfer of the cleartext contents through shared memory resources.
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.
Explicitly calls for removing confidential data from process memory, directly mitigating cleartext storage.
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.
Security testing can detect cleartext secrets in memory dumps or debug output.
Secure deletion practices reduce residual cleartext after use, but do not prevent initial storage.
DLP tooling can monitor and block processes that leave sensitive data unencrypted in memory.
Cryptographic controls can mandate encryption of sensitive data in memory, directly reducing cleartext exposure.
Secure-SDLC processes include memory-handling reviews that catch this weakness.
Secure-coding standards explicitly require avoiding plaintext storage of secrets in RAM.
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 9 (1 rule)
- V-271730 OL 9 must disable storing core dumps. prevents CWE-316