CWE-201 · Słabość
Insertion of Sensitive Information Into Sent Data
- Abstrakcja
- Bazowa
- Status
- Szkic
- Dodano
- 19 lipca 2006
- Ostatnia zmiana
- 30 kwietnia 2026
Opis
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
Skutki
Confidentiality
Read Files or Directories; Read Memory; Read Application Data
Sensitive data may be exposed to attackers.
Zapobieganie
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 · Separation of Privilege
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 separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Przykłady podatności
- 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
Słabość nadrzędna
Może też być
Słabości podrzędne
Kiedy powstaje
- Architecture and Design
- Implementation — REALIZATION: This weakness is caused during implementation of an architectural security tactic.
Dotyczy
Not Language-Specific
Uwagi
Sensitive information could include data that is sensitive in and of itself (such as credentials or private messages), or otherwise useful in the further exploitation of the system (such as internal file system structure).
Źródła
- The CLASP Application Security Process — Secure Software, Inc., 2005
Wpis z katalogu CWE 4.20.