CWE-213: Exposure of Sensitive Information Due to Incompatible Policies

Export to Word

Description

The product's intended functionality exposes information to certain actors in accordance with the developer's security policy, but this information is regarded as sensitive according to the intended security policies of other stakeholders such as the product's administrator, users, or others whose information is being processed.

Extended Description

When handling information, the developer must consider whether the information is regarded as sensitive by different stakeholders, such as users or administrators. Each stakeholder effectively has its own intended security policy that the product is expected to uphold. When a developer does not treat that information as sensitive, this can introduce a vulnerability that violates the expectations of the product's users.


ThreatScore

Threat Mapped score: 0.0

Industry: Finiancial

Threat priority: Unclassified


Observed Examples (CVEs)

Related Attack Patterns (CAPEC)

N/A


Attack TTPs

N/A

Modes of Introduction

Phase Note
Policy This can occur when the product's policy does not account for all relevant stakeholders, or when the policies of other stakeholders are not interpreted properly.
Requirements This can occur when requirements do not explicitly account for all relevant stakeholders.
Architecture and Design Communications or data exchange frameworks may be chosen that exchange or provide access to more information than strictly needed.
Implementation This can occur when the developer does not properly track the flow of sensitive information and how it is exposed, e.g., via an API.

Common Consequences

Potential Mitigations

Applicable Platforms


Demonstrative Examples

Intro: This code displays some information on a web page.

Body: The code displays a user's credit card and social security numbers, even though they aren't absolutely necessary.

Social Security Number: <%= ssn %></br>Credit Card Number: <%= ccn %>

Notes

← Back to CWE list