Description
The behavior of this function is undefined unless its control parameter is set to a specific value.
Potential Impact
Other
Quality Degradation, Varies by Context
Detection Methods
- Automated Static Analysis High — Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then sea
Related Weaknesses
Taxonomy Mappings
- 7 Pernicious Kingdoms: — Undefined Behavior
- Software Fault Patterns: SFP1 — Glitch in computation
Frequently Asked Questions
What is CWE-475?
CWE-475 (Undefined Behavior for Input to API) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Base-level weakness. The behavior of this function is undefined unless its control parameter is set to a specific value.
How can CWE-475 be exploited?
Attackers can exploit CWE-475 (Undefined Behavior for Input to API) to quality degradation, varies by context. This weakness is typically introduced during the Architecture and Design, Implementation phase of software development.
How do I prevent CWE-475?
Follow secure coding practices, conduct code reviews, and use automated security testing tools (SAST/DAST) to detect this weakness early in the development lifecycle.
What is the severity of CWE-475?
CWE-475 is classified as a Base-level weakness (Medium abstraction). Its actual severity depends on the specific context and how the weakness manifests in your application.