CWE-1428—Reliance on HTTP instead of HTTPS

Weakness Name

Reliance on HTTP instead of HTTPS

Description

The product provides or relies on use of HTTP communications when HTTPS is available.

Because HTTP communications are not encrypted, HTTP is subject to various attacks against confidentiality, integrity, and authenticity. However, unlike many other protocols, HTTPS is widely available as a more secure alternative, because it uses encryption.

Common Consequences

Scope:

Confidentiality, Integrity

Impact:

Read Application Data, Modify Application Data

Notes:

HTTP can be subjected to attacks against confidentiality (by reading cleartext packets); integrity (by modifying sessions); and authenticity (by compromising servers and/or clients using cache poisoning, phishing, or other attacks that enable attackers to spoof a legitimate entity in the communication channel).

Related Weaknesses

• CWE-319Cleartext Transmission of Sensitive InformationHigh