Insertion of Sensitive Information Into Sent Data
Draft Base
Structure: Simple
Description
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
Common Consequences 1
Scope: Confidentiality
Impact: Read Files or DirectoriesRead MemoryRead Application Data
Sensitive data may be exposed to attackers.
Detection Methods 1
Automated Static AnalysisHigh
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)Potential Mitigations 4
Phase: 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.
Phase: 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.
Phase: System Configuration
Setup default error messages so that unexpected errors do not disclose sensitive information.
Phase: Architecture and Design
Strategy: 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.
Demonstrative Examples 1
ID : DX-129
The following is an actual MySQL error statement:Code Example:
Result
SQL
sqlThe error clearly exposes the database credentials.
Observed Examples 1
CVE-2022-0708Collaboration platform does not clear team emails in a response, allowing leak of email addresses
References 1
The CLASP Application Security Process
Secure Software, Inc.
2005
ID: REF-18
Applicable Platforms
Languages:
Not Language-Specific : Undetermined
Modes of Introduction
Architecture and Design
Implementation
Related Attack Patterns
- 12ASP.NET Misconfiguration: Missing Custom Error Page
- 217DEPRECATED: Failure to Protect Stored Data from Modification
- 612Improper Authorization of Index Containing Sensitive Information
- 613Insufficient Session Expiration
- 618Exposed Unsafe ActiveX Method
- 619Dangling Database Cursor ('Cursor Injection')
- 621Variable Extraction Error
- 622Improper Validation of Function Hook Arguments
- 623Unsafe ActiveX Control Marked Safe For Scripting
Related Weaknesses
Taxonomy Mapping
- CLASP
Notes
OtherSensitive 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).