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.
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).
Modes of Introduction:
– Implementation
Related Weaknesses
Consequences
Confidentiality: Read Files or Directories, Read Memory, Read Application Data
Sensitive data may be exposed to attackers.
Potential Mitigations
Phase: Requirements
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: Implementation
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: System Configuration
Description:
Setup default error messages so that unexpected errors do not disclose sensitive information.
Phase: Architecture and Design
Description: