CWE-440: Expected Behavior Violation

BaseDraft

A feature, API, or function does not perform according to its specification.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Frequently Asked Questions

What is CWE-440: Expected Behavior Violation?+

CWE-440: Expected Behavior Violation is a Common Weakness Enumeration (CWE) entry maintained by MITRE. A feature, API, or function does not perform according to its specification.

What are the security consequences of Expected Behavior Violation?+

If exploited, CWE-440 (Expected Behavior Violation) it can compromise Other, leading to outcomes such as Quality Degradation and Varies by Context.

Which programming languages are affected by Expected Behavior Violation?+

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

What are real-world examples of Expected Behavior Violation?+

MITRE documents real CVEs mapped to CWE-440, including CVE-2003-0187, CVE-2003-0465 and CVE-2005-3265. 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-440 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