CWE-318: Cleartext Storage of Sensitive Information in Executable
The product stores sensitive information in cleartext in an executable.
View on MITREExtended Description
Attackers can reverse engineer binary code to obtain secret data. This is especially easy when the cleartext is plain ASCII. 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.
Technical Details
- Structure
- Simple
Applicable To
Security Consequences
Scope
Impact
Mitigation Strategies
No mitigation information available for this CWE.
Detection Methods
No detection method information available for this CWE.
Code Examples & CVEs
Observed CVE Examples (2)
Product stores RSA private key in a DLL and uses it to sign a certificate, allowing spoofing of servers and Adversary-in-the-Middle (AITM) attacks.
View DetailsCWE Relationships
No relationship information available for this CWE.
Frequently Asked Questions
What is CWE-318: Cleartext Storage of Sensitive Information in Executable?+
CWE-318: Cleartext Storage of Sensitive Information in Executable is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product stores sensitive information in cleartext in an executable. Attackers can reverse engineer binary code to obtain secret data. This is especially easy when the cleartext is plain ASCII. 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.
What are the security consequences of Cleartext Storage of Sensitive Information in Executable?+
If exploited, CWE-318 (Cleartext Storage of Sensitive Information in Executable) it can compromise Confidentiality, leading to outcomes such as Read Application Data.
Which programming languages are affected by Cleartext Storage of Sensitive Information in Executable?+
CWE-318 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 Cleartext Storage of Sensitive Information in Executable?+
MITRE documents real CVEs mapped to CWE-318, including CVE-2005-1794 and CVE-2001-1527. 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-318 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.