CWE-537: Java Runtime Error Message Containing Sensitive Information
In many cases, an attacker can leverage the conditions that cause unhandled exception errors in order to gain unauthorized access to the system.
View on MITRETechnical Details
- Structure
- Simple
Applicable To
Security Consequences
Scope
Impact
Mitigation Strategies
Phase
Description
Do not expose sensitive error information to the user.
Detection Methods
No detection method information available for this CWE.
Code Examples & CVEs
Demonstrative Examples
In the following Java example the class InputFileRead enables an input file to be read using a FileReader object. In the constructor of this class a default input file path is set to some directory on the local file system and the method setInputFile must be called to set the name of the input file to be read in the default directory. The method readInputFile will create the FileReader object and will read the contents of the file. If the method setInputFile is not called prior to calling the method readInputFile then the File object will remain null when initializing the FileReader object. A Java RuntimeException will be raised, and an error message will be output to the user.
However, the error message output to the user contains information regarding the default directory on the local file system. This information can be exploited and may lead to unauthorized access or use of the system. Any Java RuntimeExceptions that are handled should not expose sensitive information to the user.
In the example below, the BankManagerLoginServlet servlet class will process a login request to determine if a user is authorized to use the BankManager Web service. The doPost method will retrieve the username and password from the servlet request and will determine if the user is authorized. If the user is authorized the servlet will go to the successful login page. Otherwise, the servlet will raise a FailedLoginException and output the failed login message to the error page of the service.
However, the output message generated by the FailedLoginException includes the user-supplied password. Even if the password is erroneous, it is probably close to the correct password. Since it is printed to the user's page, anybody who can see the screen display will be able to see the password. Also, if the page is cached, the password might be written to disk.
CWE Relationships
Frequently Asked Questions
What is CWE-537: Java Runtime Error Message Containing Sensitive Information?+
CWE-537: Java Runtime Error Message Containing Sensitive Information is a Common Weakness Enumeration (CWE) entry maintained by MITRE. In many cases, an attacker can leverage the conditions that cause unhandled exception errors in order to gain unauthorized access to the system.
What are the security consequences of Java Runtime Error Message Containing Sensitive Information?+
If exploited, CWE-537 (Java Runtime Error Message Containing Sensitive Information) it can compromise Confidentiality, leading to outcomes such as Read Application Data.
How do you prevent or mitigate Java Runtime Error Message Containing Sensitive Information?+
Recommended mitigations for CWE-537 include: Do not expose sensitive error information to the user.
Which programming languages are affected by Java Runtime Error Message Containing Sensitive Information?+
CWE-537 commonly affects Java. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
What is the difference between a CWE and a CVE?+
A CWE (Common Weakness Enumeration) like CWE-537 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.