CWE · MITRE source
CWE-197Numeric Truncation Error
Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.
When a primitive is cast to a smaller primitive, the high order bits of the large value are lost in the conversion, potentially resulting in an unexpected value that is not equal to the original value. This value may be required as an index into a buffer, a loop iterator, or simply necessary state data. In any case, the value cannot be trusted and the system will be in an undefined state. While this method may be employed viably to isolate the low bits of a value, this usage is rare, and truncation usually implies that an implementation error has occurred.
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 · 3 mapping(s) from 1 framework(s): ATT&CK 3 (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-2022-42475 KEV | 10.0 | 9.8 | 0.9947 | 2023-01-02 |
CVE-2025-6965 UPD | 8.0 | 7.7 | 0.7349 | 2025-07-15 |
CVE-2020-15202 | 7.0 | 9.0 | 0.0123 | 2020-09-25 |
CVE-2024-43639 | 7.0 | 9.8 | 0.0875 | 2024-11-12 |
CVE-2024-21310 UPD | 6.0 | 7.8 | 0.1151 | 2024-01-09 |
CVE-2022-34670 | 5.5 | 7.8 | 0.0027 | 2022-12-30 |
CVE-2022-34676 | 5.5 | 7.1 | 0.0026 | 2022-12-30 |
CVE-2023-35328 | 5.5 | 7.8 | 0.0042 | 2023-07-11 |
CVE-2023-36710 | 5.5 | 7.8 | 0.0111 | 2023-10-10 |
CVE-2024-21352 UPD | 5.5 | 8.8 | 0.0163 | 2024-02-13 |
CVE-2024-21391 UPD | 5.5 | 8.8 | 0.0163 | 2024-02-13 |
CVE-2024-21434 UPD | 5.5 | 7.8 | 0.0083 | 2024-03-12 |
CVE-2024-21440 UPD | 5.5 | 8.8 | 0.0203 | 2024-03-12 |
CVE-2024-21451 UPD | 5.5 | 8.8 | 0.0195 | 2024-03-12 |
CVE-2024-28944 UPD | 5.5 | 8.8 | 0.0235 | 2024-04-09 |
CVE-2024-29050 UPD | 5.5 | 8.4 | 0.0125 | 2024-04-09 |
CVE-2023-32143 | 5.5 | 8.8 | 0.0113 | 2024-05-03 |
CVE-2024-30009 | 5.5 | 8.8 | 0.0171 | 2024-05-14 |
CVE-2024-30014 | 5.5 | 7.5 | 0.0149 | 2024-05-14 |
CVE-2024-30015 | 5.5 | 7.5 | 0.0149 | 2024-05-14 |
CVE-2024-30022 | 5.5 | 7.5 | 0.0154 | 2024-05-14 |
CVE-2024-30023 | 5.5 | 7.5 | 0.0154 | 2024-05-14 |
CVE-2024-30024 | 5.5 | 7.5 | 0.0154 | 2024-05-14 |
CVE-2024-30029 | 5.5 | 7.5 | 0.0149 | 2024-05-14 |
CVE-2024-38044 | 5.5 | 7.2 | 0.0214 | 2024-07-09 |