CWE-129: Improper Validation of Array Index

VariantDraftExploit Likelihood: High

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.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
CC++Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-129 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-129, Improper Validation of Array Index, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Apply Input Validation controls for Improper Validation of Array Index

MITRE associates mitigation with Architecture and Design, Requirements, Operation, Build and Compilation, and Implementation; the listed strategies include Input Validation, Language Selection, Environment Hardening, and Sandbox or Jail; documented detection approaches include Automated Static Analysis, Automated Dynamic Analysis, and Black Box. Use these source-defined anchors to turn CWE-129 into implementation, review, and verification checks for the affected component.

CWE-129: Improper Validation of Array IndexMITRE CWE

Triage CWE-129 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-129, Improper Validation of Array Index, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-129

Apply MITRE's full root-cause mapping guidance when using CWE-129, Improper Validation of Array Index. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping GuidanceMITRE CWE

Validate CWE-129 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-129, Improper Validation of Array Index. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick TipsMITRE CWE

Frequently Asked Questions

What is CWE-129: Improper Validation of Array Index?+

CWE-129: Improper Validation of Array Index is a Common Weakness Enumeration (CWE) entry maintained by MITRE. 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.

What are the security consequences of Improper Validation of Array Index?+

If exploited, CWE-129 (Improper Validation of Array Index) it can compromise Integrity, Availability and Confidentiality, leading to outcomes such as DoS: Crash, Exit, or Restart, Modify Memory, Read Memory and Execute Unauthorized Code or Commands.

How is Improper Validation of Array Index detected?+

CWE-129 can be detected using Black Box. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Improper Validation of Array Index?+

CWE-129 commonly affects C, C++ and Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Improper Validation of Array Index?+

MITRE documents real CVEs mapped to CWE-129, including CVE-2005-0369, CVE-2001-1009, CVE-2003-0721, CVE-2004-1189 and CVE-2007-5756. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-129 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Advertisement