CWE · MITRE source
CWE-1285Improper Validation of Specified Index, Position, or Offset in Input
The product receives input that is expected to specify an index, position, or offset into an indexable resource such as a buffer or file, but it does not validate or incorrectly validates that the specified index/position/offset has the required properties.
Often, indexable resources such as memory buffers or files can be accessed using a specific position, index, or offset, such as an index for an array or a position for a file. When untrusted input is not properly validated before it is used as an index, attackers could access (or attempt to access) unauthorized portions of these resources. This could be used to cause buffer overflows, excessive resource allocation, or trigger unexpected failures.
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: full · 10 mapping(s) from 2 framework(s): ASVS 5.0 5 (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-2025-3357 UPD | 7.0 | 9.8 | 0.0082 | 2025-05-28 |
CVE-2025-3755 UPD | 7.0 | 9.1 | 0.0069 | 2025-05-29 |
CVE-2025-55086 | 7.0 | 9.8 | 0.0036 | 2025-10-20 |
CVE-2025-67268 UPD | 7.0 | 9.8 | 0.0067 | 2026-01-02 |
CVE-2026-33557 UPD | 7.0 | 9.1 | 0.0058 | 2026-04-20 |
CVE-2020-25241 | 5.5 | 7.5 | 0.0103 | 2021-03-15 |
CVE-2022-21821 | 5.5 | 7.8 | 0.0201 | 2022-03-29 |
CVE-2022-22201 | 5.5 | 7.5 | 0.0062 | 2022-10-18 |
CVE-2023-39388 | 5.5 | 7.5 | 0.0038 | 2023-08-13 |
CVE-2023-39389 | 5.5 | 7.5 | 0.0038 | 2023-08-13 |
CVE-2023-46724 | 5.5 | 8.6 | 0.0401 | 2023-11-01 |
CVE-2024-23609 UPD | 5.5 | 7.8 | 0.0059 | 2024-03-11 |
CVE-2024-23612 UPD | 5.5 | 7.8 | 0.0060 | 2024-03-11 |
CVE-2024-41928 | 5.5 | 8.4 | 0.0024 | 2024-09-05 |
CVE-2024-51564 | 5.5 | 7.5 | 0.0044 | 2024-11-12 |
CVE-2024-10494 | 5.5 | 7.8 | 0.0019 | 2024-12-10 |
CVE-2024-10495 | 5.5 | 7.8 | 0.0019 | 2024-12-10 |
CVE-2024-10496 | 5.5 | 7.8 | 0.0019 | 2024-12-10 |
CVE-2025-2633 UPD | 5.5 | 7.8 | 0.0016 | 2025-07-23 |
CVE-2025-2634 UPD | 5.5 | 7.8 | 0.0016 | 2025-07-23 |
CVE-2025-7848 UPD | 5.5 | 7.8 | 0.0022 | 2025-07-29 |
CVE-2025-7849 UPD | 5.5 | 7.8 | 0.0023 | 2025-07-29 |
CVE-2025-57774 UPD | 5.5 | 7.8 | 0.0025 | 2025-09-02 |
CVE-2025-57775 UPD | 5.5 | 7.8 | 0.0025 | 2025-09-02 |
CVE-2025-57776 UPD | 5.5 | 7.8 | 0.0025 | 2025-09-02 |