CWE-312Cleartext Storage of Sensitive Information

Description

Common consequences· 1

• Confidentiality — Read Application Data
  An attacker with access to the system could read sensitive information stored in cleartext (i.e., unencrypted). Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.

Potential mitigations· 2

• [Implementation, System Configuration, Operation]When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to encrypt the data at rest. [REF-1297] [REF-1299] [REF-1301]
• [Implementation, System Configuration, Operation]In some systems/environments such as cloud, the use of "double encryption" (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.

Related CAPEC attack patterns· 1

Exploits (incoming)1

Compliance frameworks addressing this (incoming)6

(incoming)13

Related by meaning· 6

Nearest entities by semantic similarity across the cs-graph corpus.