CWE-201: Insertion of Sensitive Information Into Sent Data
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
View on MITRETechnical Details
- Structure
- Simple
Applicable To
Security Consequences
Scope
Impact
Sensitive data may be exposed to attackers.
Mitigation Strategies
Phase
Description
Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
Phase
Description
Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere. Any information that is not necessary to the functionality should be removed in order to lower both the overhead and the possibility of security sensitive data being sent.
Phase
Description
Setup default error messages so that unexpected errors do not disclose sensitive information.
Detection Methods
No detection method information available for this CWE.
Code Examples & CVEs
Observed CVE Examples (1)
Collaboration platform does not clear team emails in a response, allowing leak of email addresses
View DetailsCWE Relationships
No relationship information available for this CWE.
Frequently Asked Questions
What is CWE-201: Insertion of Sensitive Information Into Sent Data?+
CWE-201: Insertion of Sensitive Information Into Sent Data is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
What are the security consequences of Insertion of Sensitive Information Into Sent Data?+
If exploited, CWE-201 (Insertion of Sensitive Information Into Sent Data) it can compromise Confidentiality, leading to outcomes such as Read Files or Directories, Read Memory and Read Application Data.
How do you prevent or mitigate Insertion of Sensitive Information Into Sent Data?+
Recommended mitigations for CWE-201 include: Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data. Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere. Any information that is not necessary to the functionality should be removed in order to lower both the overhead and the possibility of security sensitive data being sent. Setup default error messages so that unexpected errors do not disclose sensitive information.
Which programming languages are affected by Insertion of Sensitive Information Into Sent Data?+
CWE-201 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
What are real-world examples of Insertion of Sensitive Information Into Sent Data?+
MITRE documents real CVEs mapped to CWE-201, including CVE-2022-0708. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.
What is the difference between a CWE and a CVE?+
A CWE (Common Weakness Enumeration) like CWE-201 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.