CWE · MITRE source
CWE-131Incorrect Calculation of Buffer Size
The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow.
Last updated: 19 November 2026 23:37 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: full · 29 mapping(s) from 4 framework(s): ATT&CK 19 (full) · ISO_IEC_27002_2022 5 (partial) · 800-53 4 (mostly) · 1 (mostly)
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (0)
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| 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).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2003-0899 UPD | 8.6 | 9.8 | 0.2219 | 2003-11-03 |
CVE-2005-3120 UPD | 8.6 | 9.8 | 0.2326 | 2005-10-17 |
CVE-2026-42945 UPD | 8.6 | 8.1 | 0.6805 | 2026-05-13 |
CVE-2001-0249 UPD | 8.5 | 9.8 | 0.1975 | 2001-06-18 |
CVE-2020-17087 KEV UPD | 8.5 | 7.8 | 0.0543 | 2020-11-11 |
CVE-2005-2103 UPD | 8.4 | 9.8 | 0.1605 | 2005-08-16 |
CVE-2020-8450 UPD | 8.3 | 7.3 | 0.7179 | 2020-02-04 |
CVE-2001-0248 UPD | 8.2 | 9.8 | 0.1117 | 2001-06-18 |
CVE-2004-1363 UPD | 8.2 | 9.8 | 0.0910 | 2004-08-04 |
CVE-2008-0599 UPD | 8.2 | 9.8 | 0.1092 | 2008-05-05 |
CVE-2020-6113 UPD | 8.2 | 7.8 | 0.6414 | 2020-09-17 |
CVE-2002-1347 UPD | 8.1 | 9.8 | 0.0708 | 2002-12-18 |
CVE-2004-0434 UPD | 8.1 | 9.8 | 0.0716 | 2004-07-07 |
CVE-2023-36824 UPD | 8.1 | 7.4 | 0.7742 | 2023-07-11 |
CVE-2021-0254 UPD | 7.7 | 9.8 | 0.0266 | 2021-04-22 |
CVE-2024-23621 UPD | 7.7 | 10.0 | 0.0185 | 2024-01-26 |
CVE-2024-23622 UPD | 7.7 | 10.0 | 0.0185 | 2024-01-26 |
CVE-2019-10627 UPD | 7.6 | 9.8 | 0.0135 | 2019-11-21 |
CVE-2020-11901 UPD | 7.6 | 9.0 | 0.2161 | 2020-06-17 |
CVE-2020-15350 UPD | 7.6 | 9.8 | 0.0147 | 2020-07-07 |
CVE-2024-23606 UPD | 7.6 | 9.8 | 0.0168 | 2024-02-20 |
CVE-2019-10500 UPD | 7.5 | 9.8 | 0.0090 | 2019-12-18 |
CVE-2021-27378 UPD | 7.5 | 9.8 | 0.0125 | 2021-02-18 |
CVE-2021-21824 UPD | 7.5 | 9.8 | 0.0121 | 2021-06-11 |
CVE-2023-24819 UPD | 7.5 | 9.8 | 0.0098 | 2023-04-24 |