CWE-537: Java Runtime Error Message Containing Sensitive Information

VariantIncomplete

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 MITRE
Back to CWE Lookup

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Java
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-537 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-537, Java Runtime Error Message Containing Sensitive Information, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development FrameworkNational Institute of Standards and Technology

Address Java Runtime Error Message Containing Sensitive Information during Implementation

MITRE associates mitigation with Implementation; recorded impacts include Read Application Data; related weaknesses include CWE-211. Use these source-defined anchors to turn CWE-537 into implementation, review, and verification checks for the affected component.

CWE-537: Java Runtime Error Message Containing Sensitive InformationMITRE CWE

Triage CWE-537 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-537, Java Runtime Error Message Containing Sensitive Information, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities CatalogCybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-537

Apply MITRE's full root-cause mapping guidance when using CWE-537, Java Runtime Error Message Containing Sensitive Information. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping GuidanceMITRE CWE

Validate CWE-537 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-537, Java Runtime Error Message Containing Sensitive Information. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick TipsMITRE CWE

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.

Learn More

Advertisement