CWE-206: Observable Internal Behavioral Discrepancy

VariantIncomplete

The product performs multiple behaviors that are combined to produce a single result, but the individual behaviors are observable separately in a way that allows attackers to reveal internal state or internal decision points.

View on MITRE
Back to CWE Lookup

Extended Description

Ideally, a product should provide as little information as possible to an attacker. Any hints that the attacker may be making progress can then be used to simplify or optimize the attack. For example, in a login procedure that requires a username and password, ultimately there is only one decision: success or failure. However, internally, two separate actions are performed: determining if the username exists, and checking if the password is correct. If the product behaves differently based on whether the username exists or not, then the attacker only needs to concentrate on the password.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-206 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-206, Observable Internal Behavioral Discrepancy, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Make elimination of CWE-206 a product outcome

Apply CISA's Secure by Design principle of taking ownership of customer security outcomes to CWE-206, Observable Internal Behavioral Discrepancy. Put the weakness in the product threat model and security roadmap, fund class-level design and platform changes, prefer safe defaults and reusable guardrails, and publish measurable progress. Do not transfer the primary burden to customer configuration when the manufacturer can remove or contain the root cause in the product.

Shifting the Balance of Cybersecurity Risk: Secure by Design SoftwareCybersecurity and Infrastructure Security Agency

Connect Observable Internal Behavioral Discrepancy to documented attack evidence

Recorded impacts include Read Application Data, and Bypass Protection Mechanism; observed examples include CVE-2002-2031, CVE-2005-2025, and CVE-2001-1497; related weaknesses include CWE-205. Use these source-defined anchors to turn CWE-206 into implementation, review, and verification checks for the affected component.

CWE-206: Observable Internal Behavioral DiscrepancyMITRE CWE

Apply precise root-cause mapping to CWE-206

Apply MITRE's full root-cause mapping guidance when using CWE-206, Observable Internal Behavioral Discrepancy. 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 GuidanceMITRE CWE

Validate CWE-206 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-206, Observable Internal Behavioral Discrepancy. 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 TipsMITRE CWE

Frequently Asked Questions

What is CWE-206: Observable Internal Behavioral Discrepancy?+

CWE-206: Observable Internal Behavioral Discrepancy is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product performs multiple behaviors that are combined to produce a single result, but the individual behaviors are observable separately in a way that allows attackers to reveal internal state or internal decision points. Ideally, a product should provide as little information as possible to an attacker. Any hints that the attacker may be making progress can then be used to simplify or optimize the attack. For example, in a login procedure that requires a username and password, ultimately there is only one decision: success or failure. However, internally, two separate actions are performed: determining if the username exists, and checking if the password is correct. If the product behaves differently based on whether the username exists or not, then the attacker only needs to concentrate on the password.

What are the security consequences of Observable Internal Behavioral Discrepancy?+

If exploited, CWE-206 (Observable Internal Behavioral Discrepancy) it can compromise Confidentiality and Access Control, leading to outcomes such as Read Application Data and Bypass Protection Mechanism.

How do you prevent or mitigate Observable Internal Behavioral Discrepancy?+

Recommended mitigations for CWE-206 include: Setup generic response pages for error conditions. The error page should not disclose information about the success or failure of a sensitive operation. For instance, the login page should not confirm that the login is correct and the password incorrect. The attacker who tries random account name may be able to guess some of them. Confirming that the account exists would make the login page more susceptible to brute force attack.

Which programming languages are affected by Observable Internal Behavioral Discrepancy?+

CWE-206 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 Observable Internal Behavioral Discrepancy?+

MITRE documents real CVEs mapped to CWE-206, including CVE-2002-2031, CVE-2005-2025, CVE-2001-1497 and CVE-2003-0190. 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-206 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

Advertisement