CWE WEAKNESSES / CWE-201
CWE-201
Insertion of Sensitive Information Into Sent Data
Base
What it is
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
Impact
| Confidentiality | Read Files or Directories, Read Memory, Read Application Data |
Mitigations
- [Requirements] Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
- [Implementation] 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.
- [System Configuration] Setup default error messages so that unexpected errors do not disclose sensitive information.
- [Architecture and Design]Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separ
Real-world CVE examples
- CVE-2023-27265 — collaboration platform does not honor a "show email address" setting for a response by an API endpoint
- CVE-2023-32275 — RPC server for a VPN product returns an object that contains heap addresses
- CVE-2022-0708 — Collaboration platform does not clear team emails in a response, allowing leak of email addresses
Related weaknesses
Test & detect
Browse all common weaknesses, check related exploited CVEs, or map to ATT&CK techniques.
Source: MITRE CWE. View on cwe.mitre.org →