CWE-200
Exposure of Sensitive Information to an Unauthorized Actor
Description
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
{"xhtml:p":["There are many different kinds of mistakes that introduce information exposures. The severity of the error can range widely, depending on the context in which the product operates, the type of sensitive information that is revealed, and the benefits it may provide to an attacker. Some kinds of sensitive information include:","Information might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:","Information exposures can occur in different ways:","It is common practice to describe any loss of confidentiality as an \"information exposure,\" but this can lead to overuse of CWE-200 in CWE mapping. From the CWE perspective, loss of confidentiality is a technical impact that can arise from dozens of different weaknesses, such as insecure file permissions or out-of-bounds read. CWE-200 and its lower-level descendants are intended to cover the mistakes that occur in behaviors that explicitly manage, store, transfer, or cleanse sensitive information."],"xhtml:ul":[{"xhtml:li":["private, personal information, such as personal messages, financial data, health records, geographic location, or contact details","system status and environment, such as the operating system and installed packages","business secrets and intellectual property","network status and configuration","the product's own code or internal state","metadata, e.g. logging of connections or message headers","indirect information, such as a discrepancy between two internal operations that can be observed by an outsider"]},{"xhtml:li":["the product's own users","people or organizations whose information is created or used by the product, even if they are not direct product users","the product's administrators, including the admins of the system(s) and/or networks on which the product operates","the developer"]},{"xhtml:li":[{"_":"the code sensitive information into resources or messages that are intentionally made accessible to unauthorized actors, but should not contain the information - i.e., the information should have been \"scrubbed\" or \"sanitized\"","xhtml:b":["explicitly inserts"]},{"_":"a different weakness or mistake the sensitive information into resources, such as a web script error revealing the full system path of the program.","xhtml:b":["indirectly inserts"]},{"_":"the code manages resources that intentionally contain sensitive information, but the resources are to unauthorized actors. In this case, the information exposure is resultant - i.e., a different weakness enabled the access to the information in the first place.","xhtml:b":["unintentionally made accessible"]}]}]}
Parent Weaknesses (ChildOf)
Common Consequences
Scope
Impact
Read Application Data
Potential Mitigations
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
CVE-2022-31162Rust library leaks Oauth client details in application debug logs
CVE-2021-25476Digital Rights Management (DRM) capability for mobile platform leaks pointer information, simplifying ASLR bypass
CVE-2001-1483Enumeration of valid usernames based on inconsistent responses
CVE-2001-1528Account number enumeration via inconsistent responses.
CVE-2004-2150User enumeration via discrepancies in error messages.
CVE-2005-1205Telnet protocol allows servers to obtain sensitive environment information from clients.
CVE-2002-1725Script calls phpinfo(), revealing system configuration to web user
CVE-2002-0515Product sets a different TTL when a port is being filtered than when it is not being filtered, which allows remote attackers to identify filtered ports by comparing TTLs.
CVE-2004-0778Version control system allows remote attackers to determine the existence of arbitrary files and directories via the -X command for an alternate history file, which causes different error messages to be returned.
CVE-2000-1117Virtual machine allows malicious web site operators to determine the existence of files on the client by measuring delays in the execution of the getSystemResource method.
+9 more examples
Applicable Platforms
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now