CWE-319: Cleartext Transmission of Sensitive Information

Code Examples & CVEs

Demonstrative Examples

The following code attempts to establish a connection to a site to communicate sensitive information.

Though a connection is successfully made, the connection is unencrypted and it is possible that all sensitive data sent to or received from the server will be read by unintended actors.

BadJava

try {URL u = new URL("http://www.secret.example.org/");HttpURLConnection hu = (HttpURLConnection) u.openConnection();hu.setRequestMethod("PUT");hu.connect();OutputStream os = hu.getOutputStream();hu.disconnect();}catch (IOException e) {                            //...                                                  }

The following Azure CLI command lists the properties of a particular storage account:

The JSON result might be:

BadJSON

{ 		    		     "name": "{StorageAccountName}", 		     "enableHttpsTrafficOnly": false, 		     "type": "Microsoft.Storage/storageAccounts" 		    		   }

The following Azure CLI command lists the properties of a particular storage account:

The JSON result might be:

GoodShell

az storage account update -g {ResourceGroupName} -n {StorageAccountName} --https-only true

The following Azure CLI command lists the properties of a particular storage account:

The JSON result might be:

GoodJSON

{ 		    		     "name": "{StorageAccountName}", 		     "enableHttpsTrafficOnly": true, 		     "type": "Microsoft.Storage/storageAccounts" 		    		   }

Observed CVE Examples (13)

CVE-2022-29519

Programmable Logic Controller (PLC) sends sensitive information in plaintext, including passwords and session tokens.

View Details

CVE-2022-30312

Building Controller uses a protocol that transmits authentication credentials in plaintext.

View Details

CVE-2022-31204

Programmable Logic Controller (PLC) sends password in plaintext.

View Details

CVE-2002-1949

Passwords transmitted in cleartext.

View Details

CVE-2008-4122

Chain: Use of HTTPS cookie without "secure" flag causes it to be transmitted across unencrypted HTTP.

View Details

CVE-2008-3289

Product sends password hash in cleartext in violation of intended policy.

View Details

CVE-2008-4390

Remote management feature sends sensitive information including passwords in cleartext.

View Details

CVE-2007-5626

Backup routine sends password in cleartext in email.

View Details

CVE-2004-1852

Product transmits Blowfish encryption key in cleartext.

View Details

CVE-2008-0374

Printer sends configuration information, including administrative password, in cleartext.

View Details

CVE-2007-4961

Chain: cleartext transmission of the MD5 hash of password enables attacks against a server that is susceptible to replay (CWE-294).

View Details

CVE-2007-4786

Product sends passwords in cleartext to a log server.

View Details

CVE-2005-3140

Product sends file with cleartext passwords in e-mail message intended for diagnostic purposes.

View Details

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-319 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-319, Cleartext Transmission of Sensitive Information, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

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

Address Cleartext Transmission of Sensitive Information during Architecture and Design

MITRE associates mitigation with Architecture and Design, Implementation, Testing, and Operation; documented detection approaches include Black Box, and Automated Static Analysis; recorded impacts include Read Application Data, Modify Files or Directories, and Other. Use these source-defined anchors to turn CWE-319 into implementation, review, and verification checks for the affected component.

CWE-319: Cleartext Transmission of Sensitive Information — MITRE CWE

Triage CWE-319 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-319, Cleartext Transmission 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-319

Apply MITRE's full root-cause mapping guidance when using CWE-319, Cleartext Transmission 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-319 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-319, Cleartext Transmission 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-319: Cleartext Transmission of Sensitive Information?+

CWE-319: Cleartext Transmission of Sensitive Information is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

What are the security consequences of Cleartext Transmission of Sensitive Information?+

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

How do you prevent or mitigate Cleartext Transmission of Sensitive Information?+

Recommended mitigations for CWE-319 include: Before transmitting, encrypt the data using reliable, confidentiality-protecting cryptographic protocols. When using web applications with SSL, use SSL for the entire session from login to logout, not just for the initial login page. When designing hardware platforms, ensure that approved encryption algorithms (such as those recommended by NIST) protect paths from security critical data to trusted user applications.

Which programming languages are affected by Cleartext Transmission of Sensitive Information?+

CWE-319 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 Transmission of Sensitive Information?+

MITRE documents real CVEs mapped to CWE-319, including CVE-2022-29519, CVE-2022-30312, CVE-2022-31204, CVE-2002-1949 and CVE-2008-4122. 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-319 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.

CWE-319: Cleartext Transmission of Sensitive Information

Technical Details

Applicable To

Security Consequences

Scope

Impact

Scope

Impact

Mitigation Strategies

Phase

Description

Phase

Description

Phase

Description

Phase

Description

Phase

Description

Detection Methods

Code Examples & CVEs

Demonstrative Examples

Observed CVE Examples (13)

CWE Relationships

Parent Weaknesses

Source-backed guidance

Verify controls for CWE-319 with SSDF evidence

Address Cleartext Transmission of Sensitive Information during Architecture and Design

Triage CWE-319 against known exploitation evidence

Apply precise root-cause mapping to CWE-319

Validate CWE-319 with root-cause mapping checks

Frequently Asked Questions

Learn More