CWE-372: Incomplete Internal State Distinction

BaseDraft

The product does not properly determine which state it is in, causing it to assume it is in state X when in fact it is in state Y, causing it to perform incorrect operations in a security-relevant manner.

View on MITRE
Back to CWE Lookup

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Frequently Asked Questions

What is CWE-372: Incomplete Internal State Distinction?+

CWE-372: Incomplete Internal State Distinction is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product does not properly determine which state it is in, causing it to assume it is in state X when in fact it is in state Y, causing it to perform incorrect operations in a security-relevant manner.

What are the security consequences of Incomplete Internal State Distinction?+

If exploited, CWE-372 (Incomplete Internal State Distinction) it can compromise Integrity and Other, leading to outcomes such as Varies by Context and Unexpected State.

Which programming languages are affected by Incomplete Internal State Distinction?+

CWE-372 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-372 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