名称: Cleartext Storage of Sensitive Information in Memory

The product stores sensitive information in cleartext in memory.

基本信息

引入方式

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

适用平台

编程语言

类： Not Language-Specific (Undetermined)

常见后果

影响范围	影响	可能性
Confidentiality	Read Memory 注意： Memory could be read by attackers with administrator privileges, which may be a concern in some threat models. However, even without admin privileges, 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.

观察示例

参考资料	描述
CVE-2025-24870	GUI for a desktop client stores credentials in program memory, allowing privilege escalation
CVE-2001-1517	Sensitive authentication information in cleartext in memory.
CVE-2001-0984	Password protector leaves passwords in memory when window is minimized, even when "clear password when minimized" is set.
CVE-2003-0291	SSH client does not clear credentials from memory.

漏洞映射说明

依据 : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
备注 : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

备注

This could be a resultant weakness, e.g. if the compiler removes code that was intended to wipe memory.
Different people use "cleartext" and "plaintext" to mean the same thing: the lack of encryption. However, within cryptography, these have more precise meanings. Plaintext is the information just before it is fed into a cryptographic algorithm, including already-encrypted text. Cleartext is any information that is unencrypted, although it might be in an encoded form that is not easily human-readable (such as base64 encoding).

提交记录

名称	组织	日期	发布日期	Version
PLOVER		2006-07-19 +00:00	2006-07-19 +00:00	Draft 3

修改记录

名称	组织	日期	备注
Eric Dalci	Cigital	2008-07-01 +00:00	updated Time_of_Introduction
CWE Content Team	MITRE	2008-09-08 +00:00	updated Description, Relationships, Other_Notes, Relationship_Notes, Taxonomy_Mappings
CWE Content Team	MITRE	2011-06-01 +00:00	updated Common_Consequences
CWE Content Team	MITRE	2012-05-11 +00:00	updated Relationships
CWE Content Team	MITRE	2013-07-17 +00:00	updated Applicable_Platforms, Description, Name, Other_Notes, Potential_Mitigations, Terminology_Notes
CWE Content Team	MITRE	2014-07-30 +00:00	updated Relationships, Taxonomy_Mappings
CWE Content Team	MITRE	2017-11-08 +00:00	updated Modes_of_Introduction, Observed_Examples, Relationships
CWE Content Team	MITRE	2020-02-24 +00:00	updated Relationships
CWE Content Team	MITRE	2021-10-28 +00:00	updated Relationships
CWE Content Team	MITRE	2023-01-31 +00:00	updated Description
CWE Content Team	MITRE	2023-04-27 +00:00	updated Relationships
CWE Content Team	MITRE	2023-06-29 +00:00	updated Mapping_Notes
CWE Content Team	MITRE	2024-02-29 +00:00	updated Observed_Examples
CWE Content Team	MITRE	2025-12-11 +00:00	updated Relationships, Weakness_Ordinalities
CWE Content Team	MITRE	2026-04-30 +00:00	updated Observed_Examples
CWE Content Team	MITRE	2026-10-28 +00:00	updated Common_Consequences, Description

CWE-316 详情

CWE-316