CWE-205 Base Incomplete

Observable Behavioral Discrepancy

This vulnerability occurs when an application behaves differently in ways that unauthorized users can detect. These observable differences can reveal internal system logic, state information, or how…

Definition

What is CWE-205?

This vulnerability occurs when an application behaves differently in ways that unauthorized users can detect. These observable differences can reveal internal system logic, state information, or how the product varies from similar applications, providing attackers with valuable clues.
Applications should minimize information about their internal processes. When behavior varies noticeably—such as in response times, error messages, or feature availability—attackers can use these discrepancies to map the system's logic, infer sensitive data, or identify weaknesses not present in comparable software. These behavioral differences often create unintended side channels. An attacker can systematically probe these variations to simplify their attacks, bypass security controls, or gather intelligence without triggering standard detection mechanisms, making the system easier to exploit.
Real-world impact

Real-world CVEs caused by CWE-205

  • CVE-2002-0208

    Product modifies TCP/IP stack and ICMP error messages in unusual ways that show the product is in use.

  • CVE-2004-2252

    Behavioral infoleak by responding to SYN-FIN packets.

How attackers exploit it

Step-by-step attacker path

  1. 1

    Identify a code path that handles untrusted input without validation.

  2. 2

    Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.

  3. 3

    Deliver the payload through a normal request and observe the application's reaction.

  4. 4

    Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable pseudo

MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.

Vulnerable pseudo 
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}
Secure code example

Secure pseudo

Secure pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist

How to prevent CWE-205

  • Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
  • Implementation Validate input at trust boundaries; use allowlists, not denylists.
  • Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
  • Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
  • Operation Monitor logs for the runtime signals listed in the next section.
Detection signals

How to detect CWE-205

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

Plexicus auto-fix

Plexicus auto-detects CWE-205 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-205?

This vulnerability occurs when an application behaves differently in ways that unauthorized users can detect. These observable differences can reveal internal system logic, state information, or how the product varies from similar applications, providing attackers with valuable clues.

How serious is CWE-205?

MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.

What languages or platforms are affected by CWE-205?

MITRE has not specified affected platforms for this CWE — it can apply across most application stacks.

How can I prevent CWE-205?

Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.

How does Plexicus detect and fix CWE-205?

Plexicus's SAST engine matches the data-flow signature for CWE-205 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-205?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/205.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-205

CWE-203 Parent

Observable Discrepancy

This vulnerability occurs when an application responds differently to unauthorized users based on internal conditions. Attackers can…

CWE-1300 Sibling

Improper Protection of Physical Side Channels

This vulnerability occurs when a hardware device lacks adequate safeguards against physical side-channel attacks. Attackers can exploit…

CWE-1303 Sibling

Non-Transparent Sharing of Microarchitectural Resources

This vulnerability occurs when a processor's internal performance features, like caches and branch predictors, are unintentionally shared…

CWE-204 Sibling

Observable Response Discrepancy

This vulnerability occurs when an application responds differently to similar requests, unintentionally leaking details about its internal…

CWE-208 Sibling

Observable Timing Discrepancy

This vulnerability occurs when an application takes measurably different amounts of time to perform different operations, such as checking…

CWE-514 Can precede

Covert Channel

A covert channel is a hidden communication path that allows data to be transmitted in a way that bypasses the system's intended security…

CWE-206 Child

Observable Internal Behavioral Discrepancy

This vulnerability occurs when a system's internal steps or decisions become visible to an attacker because the system behaves differently…

CWE-207 Child

Observable Behavioral Discrepancy With Equivalent Products

This vulnerability occurs when a system that should remain anonymous behaves differently than other products with the same purpose,…

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.