CWEweakness
CWE-206 Observable Internal Behavioral Discrepancy
- Abstraction
- Variant
- Structure
- Simple
- Status
- Incomplete
- Languages
- Not Language-Specific
- CWE version
- 5.0
Description
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.
Common consequences
• Confidentiality, Access Control: Read Application Data, Bypass Protection Mechanism
Potential mitigations
• [Requirements, Implementation] Ideally, the 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.
• [System Configuration, Implementation] For error pages, set up 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 names may be able to guess some of them. Confirming that the account exists would make the login page more susceptible to brute force attack, or possibly leak information about the person who has the account.
Observed examples
• CVE-2002-2031: File existence via infoleak monitoring whether "onerror" handler fires or not.
• CVE-2005-2025: Valid groupname enumeration via behavioral infoleak (sends response if valid, doesn't respond if not).
• CVE-2001-1497: Behavioral infoleak in GUI allows attackers to distinguish between alphanumeric and non-alphanumeric characters in a password, thus reducing the search space.
• CVE-2003-0190: Product immediately sends an error message when user does not exist instead of waiting until the password is provided, allowing username enumeration.
Related
Observed example · CVE (4)
- CVE-2005-2025 Cisco VPN 3000 Concentrator before 4.1.7.F allows remote attackers to determine valid groupnames by sending an IKE Aggressive Mode packet… vulnerability
- CVE-2003-0190 OpenSSH-portable (OpenSSH) 3.6.1p1 and earlier with PAM support enabled immediately sends an error message when a user does not exist,… vulnerability
- CVE-2002-2031 Internet Explorer 5.0, 5.0.1 and 5.5 with JavaScript execution enabled allows remote attackers to determine the existence of arbitrary… vulnerability
- CVE-2001-1497 Microsoft Internet Explorer 4.0 through 6.0 could allow local users to differentiate between alphanumeric and non-alphanumeric characters… vulnerability
Child of · CWE (1)
- CWE-205 Observable Behavioral Discrepancy weakness
Referenced by CVE · weakness (1)
- CVE-2026-85199 Eclipse aeriOS Self-orchestrator versions prior to 1.2.1 contain a path traversal vulnerability in the REST API. vulnerability