CWE · MITRE source
CWE-316Cleartext Storage of Sensitive Information in Memory
The product stores sensitive information in cleartext in memory.
The sensitive memory might be saved to disk, stored in a core dump, or remain uncleared if the product crashes, or if the programmer does not properly clear the memory before freeing it. It could be argued that such problems are usually only exploitable by those with administrator privileges. However, swapping could cause the memory to be written to disk and leave it accessible to physical attack afterwards. Core dump files might have insecure permissions or be stored in archive files that are accessible to untrusted people. Or, uncleared sensitive memory might be inadvertently exposed to attackers due to another weakness.
Last updated: 04 July 2026 00:28 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: mostly · 5 mapping(s) from 2 framework(s): ATT&CK 4 (mostly) · STIG oracle linux 9 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A06:2025 Insecure Design.
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2025-52579 UPD | 7.0 | 9.4 | 0.0037 | 2025-07-11 |
CVE-2022-0835 | 5.5 | 8.1 | 0.0017 | 2022-04-11 |
CVE-2023-40724 | 5.5 | 7.3 | 0.0012 | 2023-09-12 |
CVE-2023-44153 | 5.5 | 7.5 | 0.0029 | 2023-09-27 |
CVE-2024-36792 | 5.5 | 8.2 | 0.0029 | 2024-06-07 |
CVE-2025-50109 UPD | 5.5 | 7.7 | 0.0012 | 2025-07-11 |
CVE-2025-9970 | 5.5 | 7.4 | 0.0009 | 2025-10-08 |
CVE-2014-2366 | 3.5 | 0.0 | 0.0131 | 2014-07-19 |
CVE-2019-3733 | 3.5 | 4.9 | 0.0060 | 2019-09-30 |
CVE-2021-32942 | 3.5 | 6.6 | 0.0018 | 2021-06-09 |
CVE-2021-23182 | 3.5 | 6.0 | 0.0017 | 2021-06-11 |
CVE-2021-23211 | 3.5 | 6.0 | 0.0011 | 2021-06-11 |
CVE-2021-31989 | 3.5 | 5.3 | 0.0040 | 2021-08-25 |
CVE-2022-33918 | 3.5 | 5.5 | 0.0013 | 2022-10-12 |
CVE-2023-3762 | 3.5 | 4.3 | 0.0033 | 2023-07-19 |
CVE-2022-46141 | 3.5 | 4.2 | 0.0014 | 2023-12-12 |
CVE-2024-25649 UPD | 3.5 | 6.7 | 0.0008 | 2024-03-14 |
CVE-2024-33900 | 3.5 | 6.5 | 0.0034 | 2024-05-20 |
CVE-2024-33901 | 3.5 | 6.5 | 0.0070 | 2024-05-20 |
CVE-2024-39732 | 3.5 | 4.1 | 0.0019 | 2024-07-14 |
CVE-2024-35282 | 3.5 | 4.2 | 0.0016 | 2024-09-10 |
CVE-2024-49800 | 3.5 | 4.3 | 0.0019 | 2025-02-06 |
CVE-2024-24915 UPD | 3.5 | 6.1 | 0.0018 | 2025-06-29 |
CVE-2025-60791 | 3.5 | 6.2 | 0.0010 | 2025-10-27 |
CVE-2025-42888 | 3.5 | 5.5 | 0.0009 | 2025-11-11 |