CWE · MITRE source
CWE-822Untrusted Pointer Dereference
The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer.
An attacker can supply a pointer for memory locations that the product is not expecting. If the pointer is dereferenced for a write operation, the attack might allow modification of critical state variables, cause a crash, or execute code. If the dereferencing operation is for a read, then the attack might allow reading of sensitive data, cause a crash, or set a variable to an unexpected value (since the value will be read from an unexpected memory location). There are several variants of this weakness, including but not necessarily limited to:
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: partial · 6 mapping(s) from 2 framework(s): ATT&CK 5 (partial) · CAPEC 1 (partial)
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-2023-29360 KEV | 10.0 | 8.4 | 0.2213 | 2023-06-14 |
CVE-2023-36033 KEV | 10.0 | 7.8 | 0.1198 | 2023-11-14 |
CVE-2024-21338 KEV UPD | 10.0 | 7.8 | 0.5187 | 2024-02-13 |
CVE-2024-35250 KEV | 10.0 | 7.8 | 0.2522 | 2024-06-11 |
CVE-2025-24990 KEV | 10.0 | 7.8 | 0.0579 | 2025-10-14 |
CVE-2023-21768 | 8.0 | 7.8 | 0.6542 | 2023-01-10 |
CVE-2018-7497 | 7.0 | 9.8 | 0.0292 | 2018-05-15 |
CVE-2018-14811 | 7.0 | 9.8 | 0.0358 | 2018-09-26 |
CVE-2018-17893 | 7.0 | 9.8 | 0.0638 | 2018-10-17 |
CVE-2018-12548 | 7.0 | 9.8 | 0.0113 | 2019-01-31 |
CVE-2023-1437 | 7.0 | 9.8 | 0.0280 | 2023-08-02 |
CVE-2023-21643 | 7.0 | 9.1 | 0.0021 | 2023-08-08 |
CVE-2024-36461 | 7.0 | 9.1 | 0.0076 | 2024-08-12 |
CVE-2025-50165 UPD | 7.0 | 9.8 | 0.0354 | 2025-08-12 |
CVE-2025-1255 | 7.0 | 9.1 | 0.0034 | 2025-09-23 |
CVE-2025-4993 | 7.0 | 9.1 | 0.0034 | 2025-09-23 |
CVE-2026-48137 | 7.0 | 9.1 | 0.0055 | 2026-06-19 |
CVE-2017-12719 | 5.5 | 7.5 | 0.0305 | 2017-11-06 |
CVE-2017-16728 | 5.5 | 7.5 | 0.0208 | 2018-01-05 |
CVE-2018-7502 | 5.5 | 7.8 | 0.0056 | 2018-03-23 |
CVE-2018-19029 | 5.5 | 7.8 | 0.0267 | 2019-02-05 |
CVE-2019-13334 | 5.5 | 7.8 | 0.0684 | 2020-02-08 |
CVE-2020-17392 | 5.5 | 8.8 | 0.0053 | 2020-08-25 |
CVE-2020-27277 | 5.5 | 7.8 | 0.0219 | 2021-01-11 |
CVE-2020-27289 | 5.5 | 7.8 | 0.0191 | 2021-01-11 |