VariantDraft
CWE-129Improper Validation of Array Index
Category: other
Description
The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.
Common consequences· 5
- Integrity / Availability — DoS: Crash, Exit, or RestartUse of an index that is outside the bounds of an array will very likely result in the corruption of relevant memory and perhaps instructions, leading to a crash, if the values are outside of the valid memory area.
- Integrity — Modify MemoryIf the memory corrupted is data, rather than instructions, the system will continue to function with improper values.
- Confidentiality / Integrity — Modify Memory, Read MemoryUse of an index that is outside the bounds of an array can also trigger out-of-bounds read or write operations, or operations on the wrong objects; i.e., "buffer overflows" are not always the result. This may result in the exposure or modification of sensitive data.
- Integrity / Confidentiality / Availability — Execute Unauthorized Code or CommandsIf the memory accessible by the attacker can be effectively controlled, it may be possible to execute arbitrary code, as with a standard buffer overflow and possibly without the use of large inputs if a precise index can be controlled.
- Integrity / Availability / Confidentiality — DoS: Crash, Exit, or Restart, Execute Unauthorized Code or Commands, Read Memory, Modify MemoryA single fault could allow either an overflow (CWE-788) or underflow (CWE-786) of the array index. What happens next will depend on the type of operation being performed out of bounds, but can expose sensitive information, cause a system crash, or possibly lead to arbitrary code execution.
Potential mitigations· 5
- [Architecture and Design]Use an input validation framework such as Struts or the OWASP ESAPI Validation API. Note that using a framework does not automatically address all input validation problems; be mindful of weaknesses that could arise from misusing the framework itself (CWE-1173).
- [Architecture and Design]
- [Requirements]
- [Operation, Build and Compilation]
- [Operation]
Related CAPEC attack patterns· 1
References
Exploits (incoming)1
| Type | Target | Confidence | Tier |
|---|---|---|---|
| AttackPattern | Overflow Bufferscapec-100 | 100% | live |
(incoming)17
| Type | Target | Confidence | Tier |
|---|---|---|---|
| Vulnerability | CVE-2025-15270cve-2025-15270 | 0% | live |
| Vulnerability | CVE-2025-15271cve-2025-15271 | 0% | live |
| Vulnerability | CVE-2025-27034cve-2025-27034 | 0% | live |
| Vulnerability | CVE-2025-3357cve-2025-3357 | 0% | live |
| Vulnerability | CVE-2025-57052cve-2025-57052 | 0% | live |
| Vulnerability | CVE-2025-5866cve-2025-5866 | 0% | live |
| Vulnerability | CVE-2025-5868cve-2025-5868 | 0% | live |
| Vulnerability | CVE-2026-2006cve-2026-2006 | 0% | live |
| Vulnerability | CVE-2026-21413cve-2026-21413 | 0% | live |
| Vulnerability | CVE-2026-22859cve-2026-22859 | 0% | live |
| Vulnerability | CVE-2026-23246cve-2026-23246 | 0% | live |
| Vulnerability | CVE-2026-3083cve-2026-3083 | 0% | live |
| Vulnerability | CVE-2026-31962cve-2026-31962 | 0% | live |
| Vulnerability | CVE-2026-31963cve-2026-31963 | 0% | live |
| Vulnerability | CVE-2026-31965cve-2026-31965 | 0% | live |
| Vulnerability | CVE-2026-31966cve-2026-31966 | 0% | live |
| Vulnerability | CVE-2026-31967cve-2026-31967 | 0% | live |
Related by meaning· 6
Nearest entities by semantic similarity across the cs-graph corpus.