CWE · MITRE source
CWE-1284Improper Validation of Specified Quantity in Input
The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.
Specified quantities include size, length, frequency, price, rate, number of operations, time, and others. Code may rely on specified quantities to allocate resources, perform calculations, control iteration, etc.
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: full · 12 mapping(s) from 2 framework(s): ASVS 5.0 7 (full) · 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-2010-3904 KEV | 10.0 | 7.8 | 0.1122 | 2010-12-06 |
CVE-2022-20699 KEV | 10.0 | 10.0 | 0.7246 | 2022-02-10 |
CVE-2021-43267 | 8.0 | 9.8 | 0.5785 | 2021-11-02 |
CVE-2008-2374 | 7.0 | 9.8 | 0.0429 | 2008-07-07 |
CVE-2009-4488 | 7.0 | 9.8 | 0.1276 | 2010-01-13 |
CVE-2021-31556 | 7.0 | 9.8 | 0.0162 | 2021-08-12 |
CVE-2021-21950 | 7.0 | 10.0 | 0.0240 | 2021-12-08 |
CVE-2021-21951 | 7.0 | 10.0 | 0.0240 | 2021-12-08 |
CVE-2021-21960 | 7.0 | 10.0 | 0.0264 | 2022-02-04 |
CVE-2022-37134 | 7.0 | 9.8 | 0.2123 | 2022-08-22 |
CVE-2022-20385 | 7.0 | 9.8 | 0.0036 | 2022-09-13 |
CVE-2022-36938 | 7.0 | 9.8 | 0.0117 | 2022-11-11 |
CVE-2022-25727 | 7.0 | 9.8 | 0.0042 | 2022-11-15 |
CVE-2024-8887 | 7.0 | 10.0 | 0.0056 | 2024-09-18 |
CVE-2024-9369 | 7.0 | 9.6 | 0.0059 | 2024-11-27 |
CVE-2024-1610 | 7.0 | 9.8 | 0.0067 | 2024-12-18 |
CVE-2025-55398 UPD | 7.0 | 9.8 | 0.0034 | 2025-08-22 |
CVE-2025-65548 | 7.0 | 9.1 | 0.0036 | 2025-12-08 |
CVE-2023-54337 | 7.0 | 9.1 | 0.0049 | 2026-01-13 |
CVE-2026-3381 | 7.0 | 9.8 | 0.0055 | 2026-03-05 |
CVE-2026-27384 | 7.0 | 9.0 | 0.0030 | 2026-03-05 |
CVE-2026-25345 | 7.0 | 9.9 | 0.0045 | 2026-03-25 |
CVE-2026-33471 | 7.0 | 9.6 | 0.0022 | 2026-04-22 |
CVE-2026-41677 | 7.0 | 9.1 | 0.0029 | 2026-04-24 |
CVE-2026-49777 UPD | 7.0 | 10.0 | 0.0166 | 2026-06-05 |