CWE-1230: Exposure of Sensitive Information Through Metadata
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.
Consequences
- Confidentiality: Read Application Data
Recent advisories
- GHSA-hf52-78x8-6w3w — Apache ActiveMQ Broker, Apache ActiveMQ, Apache ActiveMQ All have an Exposure of Sensitive Information Through Metadata vulnerability
- GHSA-879v-fggm-vxw2 — LiteLLM Has a Leakage of Langfuse API Keys
- GHSA-5r85-6h7f-rg3r — Moodle's non-searchable tags can still be discovered on the tag search page and in the tags block
- GHSA-8jg3-rx43-3fv4 — Answer vulnerable to Exposure of Sensitive Information Through Metadata
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor