CWE-475: Undefined Behavior for Input to API
The behavior of this function is undefined unless its control parameter is set to a specific value.
View on MITRETechnical Details
- Structure
- Simple
Applicable To
Security Consequences
Scope
Impact
Mitigation Strategies
No mitigation information available for this CWE.
Detection Methods
No detection method information available for this CWE.
Code Examples & CVEs
No examples or observed CVEs available for this CWE.
CWE Relationships
No relationship information available for this CWE.
Frequently Asked Questions
What is CWE-475: Undefined Behavior for Input to API?+
CWE-475: Undefined Behavior for Input to API is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The behavior of this function is undefined unless its control parameter is set to a specific value.
What are the security consequences of Undefined Behavior for Input to API?+
If exploited, CWE-475 (Undefined Behavior for Input to API) it can compromise Other, leading to outcomes such as Quality Degradation and Varies by Context.
Which programming languages are affected by Undefined Behavior for Input to API?+
CWE-475 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
What is the difference between a CWE and a CVE?+
A CWE (Common Weakness Enumeration) like CWE-475 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.