The behavior of this function is undefined unless its control parameter is set to a specific value.
View on MITRENo mitigation information available for this CWE.
No detection method information available for this CWE.
No examples or observed CVEs available for this CWE.
Additional facts reviewed against primary or authoritative security sources.
Documented detection approaches include Automated Static Analysis; recorded impacts include Quality Degradation, and Varies by Context; related weaknesses include CWE-573. Use these source-defined anchors to turn CWE-475 into implementation, review, and verification checks for the affected component.
CWE-475: Undefined Behavior for Input to API — MITRE CWEUse NIST SSDF practices to make prevention of CWE-475, Undefined Behavior for Input to API, an explicit development outcome. Translate the CWE definition into security requirements and design constraints, choose safer implementation patterns and toolchain checks, and define acceptance evidence before release. Feed every confirmed occurrence back into the requirements, design review, and coding rules so the same root cause is removed across the product rather than patched in one location.
NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and TechnologyUse CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-475, Undefined Behavior for Input to API, 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 Catalog — Cybersecurity and Infrastructure Security AgencyApply MITRE's full root-cause mapping guidance when using CWE-475, Undefined Behavior for Input to API. 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 Guidance — MITRE CWEApply MITRE's root-cause mapping quick tips to CWE-475, Undefined Behavior for Input to API. 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 Tips — MITRE CWECWE-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.
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.
CWE-475 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
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.