Comprehensive Categorization: Sensitive Information Exposure
A category in the Common Weakness Enumeration published by The MITRE Corporation.
Summary
Categories in the Common Weakness Enumeration (CWE) group entries based on some common characteristic or attribute.
Weaknesses in this category are related to sensitive information exposure.
Weaknesses
The product uses an environment variable to store unencrypted sensitive information.
A device's real time power consumption may be monitored during security token evaluation and the information gleaned may be used to determine the value of the referenc...
The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages.
The credentials necessary for unlocking a device are shared across multiple parties and may expose sensitive information.
A directory listing is inappropriately exposed, yielding potentially sensitive information to attackers.
A command shell error message indicates that there exists an unhandled exception in the web application code. In many cases, an attacker can leverage the conditions th...
The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the...
The product's intended functionality exposes information to certain actors in accordance with the developer's security policy, but this information is regarded as sens...
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the und...
The Web services architecture may require exposing a Web Service Definition Language (WSDL) file that contains information on the publicly accessible services and how ...
The product performs an operation that triggers an external diagnostic or error message that is not directly generated or controlled by the product, such as an error g...
The product generates an error message that includes sensitive information about its environment, users, or associated data.
If an include file source is accessible, the file can contain usernames and passwords, as well as sensitive information pertaining to the application and system.
Source code on a web server or repository often contains sensitive information and should generally not be accessible to users.
While adding general comments is very useful, some programmers tend to leave important data, such as: filenames related to the web application, old links or links whic...
Accessible test applications can pose a variety of security risks. Since developers or administrators rarely consider that someone besides themselves would even know a...
The product's comparison logic is performed over a series of steps rather than across the entire string in one operation. If there is a comparison logic failure on one...
The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production.
The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive ...
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
A process is invoked with sensitive command-line arguments, environment variables, or other elements that can be seen by other processes on the operating system.
In many cases, an attacker can leverage the conditions that cause unhandled exception errors in order to gain unauthorized access to the system.
The product's behaviors indicate important differences that may be observed by unauthorized actors in a way that reveals (1) its internal state or decision process, or...
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 ...
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security...
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 attac...
The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control...
Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information a...
The product identifies an error condition and creates its own diagnostic or error messages that contain sensitive information.
Certain conditions, such as network failure, will cause a server error message to be displayed.
A servlet error message indicates that there exists an unhandled exception in your web application code and may provide useful information to an attacker.
The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request.
Concepts
This view organizes weaknesses around categories that are of interest to large-scale software assurance research to support the elimination of weaknesses using ta...
See Also
Common Weakness Enumeration content on this website is copyright of The MITRE Corporation unless otherwise specified. Use of the Common Weakness Enumeration and the associated references on this website are subject to the Terms of Use as specified by The MITRE Corporation.