CWE · MITRE source
CWE-312Cleartext Storage of Sensitive Information
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
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 · 12 mapping(s) from 7 framework(s): ATT&CK 6 (mostly) · STIG oracle linux 8 1 (mostly) · STIG oracle linux 9 1 (mostly) · STIG rhel 8 1 (mostly) · OWASP-Web 1 (mostly) · CAPEC 1 (partial) · ASVS 5.0 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 (7)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-12 | Cryptographic Key Establishment and Management | SC | Key-management policy requires protected storage of key material, preventing cleartext storage of sensitive cryptographic keys. |
SC-28 | Protection of Information at Rest | SC | Requiring confidentiality protection for information at rest eliminates cleartext storage of sensitive data on persistent media. |
SC-38 | Operations Security | SC | Reduces cleartext storage of sensitive data when OPSEC identifies and mandates protection of key information artifacts. |
CM-13 | Data Action Mapping | CM | Data action mapping can detect storage actions that leave sensitive information in cleartext. |
CM-6 | Configuration Settings | CM | Configuration policies can mandate secure storage methods to avoid cleartext storage of sensitive information. |
AT-3 | Role-based Training | AT | Training on secure data handling discourages cleartext storage of sensitive information. |
MP-1 | Policy and Procedures | MP | Policy requires protection measures such as encryption for sensitive data stored on media, preventing cleartext exposure. |
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-2011-4723 KEV | 10.0 | 5.7 | 0.0313 | 2011-12-20 |
CVE-2022-26148 | 8.0 | 9.8 | 0.5344 | 2022-03-21 |
CVE-2023-50719 | 8.0 | 7.5 | 0.8355 | 2023-12-15 |
CVE-2001-1481 | 7.0 | 9.8 | 0.0290 | 2001-12-31 |
CVE-2008-0174 | 7.0 | 9.8 | 0.0196 | 2008-01-29 |
CVE-2017-5249 | 7.0 | 9.8 | 0.0070 | 2018-02-22 |
CVE-2017-5250 | 7.0 | 9.8 | 0.0070 | 2018-02-22 |
CVE-2018-18394 | 7.0 | 9.8 | 0.0071 | 2018-10-19 |
CVE-2018-18641 | 7.0 | 9.8 | 0.0093 | 2018-12-04 |
CVE-2014-5433 | 7.0 | 9.8 | 0.0206 | 2019-03-26 |
CVE-2019-0285 | 7.0 | 9.8 | 0.0661 | 2019-04-10 |
CVE-2019-11384 | 7.0 | 9.8 | 0.0099 | 2019-04-22 |
CVE-2019-9823 | 7.0 | 9.8 | 0.0157 | 2019-07-03 |
CVE-2019-9873 | 7.0 | 9.8 | 0.0156 | 2019-07-03 |
CVE-2019-13096 | 7.0 | 9.8 | 0.0114 | 2019-07-22 |
CVE-2019-19228 | 7.0 | 9.8 | 0.0190 | 2019-12-04 |
CVE-2020-5723 | 7.0 | 9.8 | 0.0570 | 2020-03-30 |
CVE-2019-18868 | 7.0 | 9.8 | 0.0084 | 2020-05-07 |
CVE-2020-9045 | 7.0 | 9.9 | 0.0099 | 2020-05-21 |
CVE-2020-12032 | 7.0 | 9.1 | 0.0094 | 2020-06-29 |
CVE-2021-29954 | 7.0 | 9.8 | 0.0064 | 2021-06-24 |
CVE-2022-25158 | 7.0 | 9.1 | 0.0132 | 2022-04-01 |
CVE-2021-36782 | 7.0 | 9.9 | 0.0293 | 2022-09-07 |
CVE-2020-15332 | 7.0 | 9.8 | 0.0088 | 2022-09-29 |
CVE-2022-43757 | 7.0 | 9.9 | 0.0055 | 2023-02-07 |