CWE · MITRE source
CWE-123Write-what-where Condition
Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.
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 · 10 mapping(s) from 5 framework(s): ATT&CK 6 (mostly) · STIG windows 10 1 (partial) · STIG windows 11 1 (partial) · STIG oracle linux 8 1 (partial) · STIG rhel 8 1 (partial)
NIST 800-53 r5 controls that address this weakness (1)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SI-16 | Memory Protection | SI | Write-what-where primitives are neutralized when the attacker cannot execute the memory they control. |
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-22225 KEV | 10.0 | 8.2 | 0.0096 | 2025-03-04 |
CVE-2026-43284 UPD | 8.0 | 8.8 | 0.9324 | 2026-05-08 |
CVE-2026-43500 UPD | 8.0 | 7.8 | 0.9277 | 2026-05-11 |
CVE-2015-8271 | 7.0 | 9.8 | 0.0592 | 2017-04-13 |
CVE-2014-5435 | 7.0 | 9.8 | 0.0347 | 2019-04-08 |
CVE-2021-38449 | 7.0 | 9.8 | 0.0118 | 2021-10-22 |
CVE-2022-38143 | 7.0 | 9.8 | 0.0142 | 2022-12-22 |
CVE-2024-42479 | 7.0 | 10.0 | 0.0263 | 2024-08-12 |
CVE-2025-69809 | 7.0 | 9.8 | 0.0053 | 2026-03-16 |
CVE-2026-30121 | 7.0 | 9.1 | 0.0032 | 2026-06-15 |
CVE-2017-10994 | 5.5 | 7.3 | 0.0494 | 2017-07-07 |
CVE-2017-6282 | 5.5 | 7.8 | 0.0015 | 2018-03-06 |
CVE-2018-12036 | 5.5 | 7.8 | 0.0171 | 2018-06-07 |
CVE-2018-16962 | 5.5 | 7.8 | 0.0052 | 2018-09-12 |
CVE-2018-3971 | 5.5 | 7.8 | 0.0054 | 2018-10-25 |
CVE-2020-2001 | 5.5 | 8.1 | 0.0133 | 2020-05-13 |
CVE-2020-16225 | 5.5 | 7.8 | 0.0209 | 2020-08-07 |
CVE-2020-7560 | 5.5 | 8.6 | 0.0139 | 2020-12-11 |
CVE-2021-42540 | 5.5 | 8.0 | 0.0097 | 2021-10-22 |
CVE-2022-40246 | 5.5 | 7.2 | 0.0046 | 2022-09-20 |
CVE-2022-40262 | 5.5 | 8.2 | 0.0031 | 2022-09-20 |
CVE-2022-35408 | 5.5 | 8.2 | 0.0034 | 2022-09-22 |
CVE-2022-41757 | 5.5 | 8.8 | 0.0068 | 2022-11-08 |
CVE-2021-45465 | 5.5 | 7.8 | 0.0032 | 2024-01-04 |
CVE-2024-20741 UPD | 5.5 | 7.8 | 0.0027 | 2024-02-15 |