The product stores sensitive information in cleartext in a file, or on disk.
View on MITREThe sensitive information could be read by attackers with access to the file, or with physical or administrator access to the raw disk. 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.
No mitigation information available for this CWE.
No detection method information available for this CWE.
The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.
This Java example shows a properties file with a cleartext username / password pair.
The following examples show a portion of properties and configuration files for Java and ASP.NET applications. The files include username and password information but they are stored in cleartext.
This Java example shows a properties file with a cleartext username / password pair.
Decrypted copy of a message written to disk given a combination of options and when user replies to an encrypted message.
View DetailsCleartext storage of private key and passphrase in log file when user imports the key.
View DetailsNo relationship information available for this CWE.
CWE-313: Cleartext Storage in a File or on Disk is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product stores sensitive information in cleartext in a file, or on disk. The sensitive information could be read by attackers with access to the file, or with physical or administrator access to the raw disk. 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.
If exploited, CWE-313 (Cleartext Storage in a File or on Disk) it can compromise Confidentiality, leading to outcomes such as Read Application Data.
CWE-313 commonly affects Not Language-Specific. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.
MITRE documents real CVEs mapped to CWE-313, including CVE-2001-1481, CVE-2005-1828, CVE-2005-2209, CVE-2002-1696 and CVE-2004-2397. You can look up the full details of each CVE, including CVSS scores and remediation guidance, on our CVE Lookup tool.
A CWE (Common Weakness Enumeration) like CWE-313 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.