COMMON WEAKNESS ENUMERATIONDraft

CWE-316

Cleartext Storage of Sensitive Information in Memory

The product stores sensitive information in cleartext in memory.

Abstraction

Variant

Structure

Simple

Likelihood of Exploit

Medium

Understand the problem

What is the problem?

The product stores sensitive information in cleartext in memory.

Extended description

The sensitive memory might be saved to disk, stored in a core dump, or remain uncleared if the product crashes, or if the programmer does not properly clear the memory before freeing it. It could be argued that such problems are usually only exploitable by those with administrator privileges. However, swapping could cause the memory to be written to disk and leave it accessible to physical attack afterwards. Core dump files might have insecure permissions or be stored in archive files that are accessible to untrusted people. Or, uncleared sensitive memory might be inadvertently exposed to attackers due to another weakness.

Root cause

How and when does the problem arise?

Lifecycle phase

Architecture and Design

OMISSION: This weakness is caused by missing a security tactic during the architecture and design phase.

Risk

What does successful exploitation lead to?

Read Memory

Affected security scopes: Confidentiality

Defence

How is it prevented and fixed?

  • Follow secure coding guidelines for input handling and boundary checking.
  • Enforce strict security reviews and automated static analysis (SAST) checks.