CWE · MITRE source
CWE-824Access of Uninitialized Pointer
The product accesses or uses a pointer that has not been initialized.
If the pointer contains an uninitialized value, then the value might not point to a valid memory location. This could cause the product to read from or write to unexpected memory locations, leading to a denial of service. If the uninitialized pointer is used as a function call, then arbitrary functions could be invoked. If an attacker can influence the portion of uninitialized memory that is contained in the pointer, this weakness could be leveraged to execute code or perform other attacks. Depending on memory layout, associated memory management behaviors, and product operation, the attacker might be able to influence the contents of the uninitialized pointer, thus gaining more fine-grained control of the memory location to be accessed.
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 · 5 mapping(s) from 1 framework(s): ATT&CK 5 (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-2015-1770 KEV | 10.0 | 8.8 | 0.3510 | 2015-06-10 |
CVE-2022-21971 KEV | 10.0 | 7.8 | 0.5365 | 2022-02-09 |
CVE-2018-9948 | 8.0 | 6.5 | 0.6407 | 2018-05-17 |
CVE-2018-11803 | 8.0 | 7.5 | 0.5782 | 2019-02-05 |
CVE-2017-12561 | 7.0 | 9.8 | 0.3111 | 2018-02-15 |
CVE-2018-11743 | 7.0 | 9.8 | 0.0220 | 2018-06-05 |
CVE-2018-14356 | 7.0 | 9.8 | 0.0317 | 2018-07-17 |
CVE-2018-17141 | 7.0 | 9.8 | 0.0559 | 2018-09-21 |
CVE-2018-19857 | 7.0 | 9.1 | 0.0392 | 2018-12-05 |
CVE-2020-17446 | 7.0 | 9.8 | 0.0242 | 2020-08-12 |
CVE-2020-25573 | 7.0 | 9.8 | 0.0178 | 2020-09-14 |
CVE-2020-11138 | 7.0 | 9.8 | 0.0109 | 2021-01-21 |
CVE-2021-1619 | 7.0 | 9.8 | 0.0170 | 2021-09-23 |
CVE-2021-36219 | 7.0 | 9.8 | 0.0158 | 2021-09-27 |
CVE-2022-42885 | 7.0 | 9.8 | 0.0082 | 2023-07-21 |
CVE-2022-44451 | 7.0 | 9.8 | 0.0082 | 2023-07-21 |
CVE-2022-46280 | 7.0 | 9.8 | 0.0084 | 2023-07-21 |
CVE-2026-2785 | 7.0 | 9.8 | 0.0037 | 2026-02-24 |
CVE-2026-2805 | 7.0 | 9.8 | 0.0040 | 2026-02-24 |
CVE-2026-6748 UPD | 7.0 | 9.8 | 0.0040 | 2026-04-21 |
CVE-2007-2442 | 6.0 | 0.0 | 0.1138 | 2007-06-26 |
CVE-2010-1818 | 6.0 | 0.0 | 0.4267 | 2010-08-31 |
CVE-2019-0853 | 6.0 | 8.8 | 0.2757 | 2019-04-09 |
CVE-2020-8882 | 6.0 | 8.8 | 0.1106 | 2020-03-20 |
CVE-2022-27794 | 6.0 | 7.8 | 0.1392 | 2022-05-11 |