CWE-1230: Exposure of Sensitive Information Through Metadata

Extended Description

Developers might correctly prevent unauthorized access to a database or other resource containing sensitive information, but they might not consider that portions of the original information might also be recorded in metadata, search indices, statistical reports, or other resources. If these resources are not also restricted, then attackers might be able to extract some or all of the original information, or otherwise infer some details. For example, an attacker could specify search terms that are known to be unique to a particular person, or view metadata such as activity or creation dates in order to identify usage patterns.

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Detect imprecise mappings involving CWE-1230

Review mappings to CWE-1230, Exposure of Sensitive Information Through Metadata, with MITRE's mapping and navigation criteria. Flag any selection that points to a View or Category, remains at a higher abstraction than the available evidence supports, or ignores relevant parent, child, peer, and alternative entries. Treat those findings as mapping-quality defects, correct them before publication, and retain the comparison trail for repeatable audits.

CWE Mapping and Navigation Guidance — MITRE CWE

Prevent CWE-1230 through an SSDF control plan

Use NIST SSDF practices to make prevention of CWE-1230, Exposure of Sensitive Information Through Metadata, an explicit development outcome. Translate the CWE definition into security requirements and design constraints, choose safer implementation patterns and toolchain checks, and define acceptance evidence before release. Feed every confirmed occurrence back into the requirements, design review, and coding rules so the same root cause is removed across the product rather than patched in one location.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Triage CWE-1230 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-1230, Exposure of Sensitive Information Through Metadata, 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 Catalog — Cybersecurity and Infrastructure Security Agency

Use MITRE taxonomy anchors to review Exposure of Sensitive Information Through Metadata

Recorded impacts include Read Application Data; related weaknesses include CWE-285. Use these source-defined anchors to turn CWE-1230 into implementation, review, and verification checks for the affected component.

CWE-1230: Exposure of Sensitive Information Through Metadata — MITRE CWE

Validate CWE-1230 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-1230, Exposure of Sensitive Information Through Metadata. 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 Tips — MITRE CWE

Frequently Asked Questions

What is CWE-1230: Exposure of Sensitive Information Through Metadata?+

CWE-1230: Exposure of Sensitive Information Through Metadata is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from the original, sensitive information. Developers might correctly prevent unauthorized access to a database or other resource containing sensitive information, but they might not consider that portions of the original information might also be recorded in metadata, search indices, statistical reports, or other resources. If these resources are not also restricted, then attackers might be able to extract some or all of the original information, or otherwise infer some details. For example, an attacker could specify search terms that are known to be unique to a particular person, or view metadata such as activity or creation dates in order to identify usage patterns.

What are the security consequences of Exposure of Sensitive Information Through Metadata?+

If exploited, CWE-1230 (Exposure of Sensitive Information Through Metadata) it can compromise Confidentiality, leading to outcomes such as Read Application Data.

Which programming languages are affected by Exposure of Sensitive Information Through Metadata?+

CWE-1230 commonly affects Not Language-Specific. 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-1230 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.

CWE-1230: Exposure of Sensitive Information Through Metadata

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Detection Methods

Code Examples & CVEs

CWE Relationships

Parent Weaknesses