Description
The product operates in an environment in which its existence or specific identity should not be known, but it behaves differently than other products with equivalent functionality, in a way that is observable to an attacker.
For many kinds of products, multiple products may be available that perform the same functionality, such as a web server, network interface, or intrusion detection system. Attackers often perform "fingerprinting," which uses discrepancies in order to identify which specific product is in use. Once the specific product has been identified, the attacks can be made more customized and efficient. Often, an organization might intentionally allow the specific product to be identifiable. However, in some environments, the ability to identify a distinct product is unacceptable, and it is expected that every product would behave in exactly the same way. In these more restricted environments, a behavioral difference might pose an unacceptable risk if it makes it easier to identify the product's vendor, model, configuration, version, etc.
Potential Impact
Confidentiality, Access Control
Read Application Data, Bypass Protection Mechanism
Real-World CVE Examples
| CVE ID | Description |
|---|---|
| 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. |
| CVE-2000-1142 | Honeypot generates an error with a "pwd" command in a particular directory, allowing attacker to know they are in a honeypot system. |
Related Weaknesses
Taxonomy Mappings
- PLOVER: — External behavioral inconsistency infoleak
Frequently Asked Questions
What is CWE-207?
CWE-207 (Observable Behavioral Discrepancy With Equivalent Products) is a software weakness identified by MITRE's Common Weakness Enumeration. It is classified as a Variant-level weakness. The product operates in an environment in which its existence or specific identity should not be known, but it behaves differently than other products with equivalent functionality, in a way that is o...
How can CWE-207 be exploited?
Attackers can exploit CWE-207 (Observable Behavioral Discrepancy With Equivalent Products) to read application data, bypass protection mechanism. This weakness is typically introduced during the Architecture and Design, Implementation phase of software development.
How do I prevent CWE-207?
Follow secure coding practices, conduct code reviews, and use automated security testing tools (SAST/DAST) to detect this weakness early in the development lifecycle.
What is the severity of CWE-207?
CWE-207 is classified as a Variant-level weakness (Low-Medium abstraction). It has been observed in 3 real-world CVEs.