CWE · MITRE source
CWE-244Improper Clearing of Heap Memory Before Release ('Heap Inspection')
Using realloc() to resize buffers that store sensitive information can leave the sensitive information exposed to attack, because it is not removed from memory.
When sensitive data such as a password or an encryption key is not removed from memory, it could be exposed to an attacker using a "heap inspection" attack that reads the sensitive data using memory dumps or other methods. The realloc() function is commonly used to increase the size of a block of allocated memory. This operation often requires copying the contents of the old memory block into a new and larger block. This operation leaves the contents of the original block intact but inaccessible to the program, preventing the program from being able to scrub sensitive data from memory. If an attacker can later examine the contents of a memory dump, the sensitive data could be exposed.
Last updated: 04 July 2026 08:17 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 · 2 mapping(s) from 1 framework(s): ATT&CK 2 (partial)
NIST 800-53 r5 controls that address this weakness (2)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-4 | Information in Shared System Resources | SC | Forces clearing of heap memory contents prior to release, preventing subsequent processes from inspecting prior sensitive data. |
SI-12 | Information Management and Retention | SI | Information management requirements drive clearing of sensitive contents from memory prior to release or reuse. |
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-26304 | 5.5 | 8.2 | 0.0036 | 2025-02-20 |
CVE-2025-26305 | 5.5 | 8.2 | 0.0036 | 2025-02-20 |
CVE-2025-5105 UPD | 5.5 | 7.3 | 0.0038 | 2025-05-23 |
CVE-2025-36118 | 5.5 | 7.5 | 0.0032 | 2025-11-17 |
CVE-2026-20039 | 5.5 | 8.6 | 0.0036 | 2026-03-04 |
CVE-2025-70873 | 5.5 | 7.5 | 0.0030 | 2026-03-12 |
CVE-2022-20922 UPD | 3.5 | 5.8 | 0.0076 | 2022-11-15 |
CVE-2022-20943 | 3.5 | 5.8 | 0.0089 | 2022-11-15 |
CVE-2023-20177 | 3.5 | 4.0 | 0.0053 | 2023-11-01 |
CVE-2023-20031 | 3.5 | 4.0 | 0.0028 | 2023-11-01 |
CVE-2023-20070 | 3.5 | 4.0 | 0.0054 | 2023-11-01 |
CVE-2025-33013 UPD | 3.5 | 6.2 | 0.0013 | 2025-07-24 |
CVE-2025-1759 UPD | 3.5 | 5.9 | 0.0031 | 2025-08-18 |
CVE-2025-36083 | 3.5 | 6.2 | 0.0011 | 2025-10-28 |
CVE-2025-45663 | 3.5 | 6.5 | 0.0034 | 2025-11-03 |
CVE-2025-1721 | 3.5 | 5.9 | 0.0029 | 2025-12-26 |
CVE-2025-1719 | 3.5 | 5.9 | 0.0033 | 2026-01-20 |
CVE-2025-1722 | 3.5 | 5.9 | 0.0033 | 2026-01-20 |
CVE-2025-33101 | 3.5 | 5.9 | 0.0020 | 2026-02-17 |