CWE-922: Insecure Storage of Sensitive Information

ClassIncomplete

The product stores sensitive information without properly limiting read or write access by unauthorized actors.

View on MITRE
Back to CWE Lookup

Extended Description

If read access is not properly restricted, then attackers can steal the sensitive information. If write access is not properly restricted, then attackers can modify and possibly delete the data, causing incorrect results and possibly a denial of service.

Technical Details

Structure
Simple

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Detect Insecure Storage of Sensitive Information with Automated Static Analysis

Documented detection approaches include Automated Static Analysis; recorded impacts include Read Application Data, Read Files or Directories, Modify Application Data, and Modify Files or Directories; observed examples include CVE-2009-2272. Use these source-defined anchors to turn CWE-922 into implementation, review, and verification checks for the affected component.

CWE-922: Insecure Storage of Sensitive Information — MITRE CWE

Prevent CWE-922 through an SSDF control plan

Use NIST SSDF practices to make prevention of CWE-922, Insecure Storage of Sensitive Information, an explicit development outcome. Translate the CWE definition into security requirements and design constraints, choose safer implementation patterns and toolchain checks, and define acceptance evidence before release. Feed every confirmed occurrence back into the requirements, design review, and coding rules so the same root cause is removed across the product rather than patched in one location.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Triage CWE-922 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-922, Insecure Storage of Sensitive Information, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-922

Apply MITRE's full root-cause mapping guidance when using CWE-922, Insecure Storage of Sensitive Information. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-922 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-922, Insecure Storage of Sensitive Information. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-922: Insecure Storage of Sensitive Information?+

CWE-922: Insecure Storage of Sensitive Information is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product stores sensitive information without properly limiting read or write access by unauthorized actors. If read access is not properly restricted, then attackers can steal the sensitive information. If write access is not properly restricted, then attackers can modify and possibly delete the data, causing incorrect results and possibly a denial of service.

What are the security consequences of Insecure Storage of Sensitive Information?+

If exploited, CWE-922 (Insecure Storage of Sensitive Information) it can compromise Confidentiality and Integrity, leading to outcomes such as Read Application Data, Read Files or Directories, Modify Application Data and Modify Files or Directories.

Which programming languages are affected by Insecure Storage of Sensitive Information?+

CWE-922 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What are real-world examples of Insecure Storage of Sensitive Information?+

MITRE documents real CVEs mapped to CWE-922, including CVE-2009-2272. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-922 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-922

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement