CWE-1428 Base Incomplete

Reliance on HTTP instead of HTTPS

This vulnerability occurs when an application uses unencrypted HTTP connections instead of the secure HTTPS alternative, even when HTTPS is available.

Definition

What is CWE-1428?

This vulnerability occurs when an application uses unencrypted HTTP connections instead of the secure HTTPS alternative, even when HTTPS is available.
Using HTTP exposes all data transmitted between the client and server, including sensitive information like login credentials, session tokens, and personal data. Attackers can easily intercept, read, or modify this unencrypted traffic through man-in-the-middle attacks, leading to data breaches, account hijacking, and content manipulation. HTTPS solves this by encrypting communications with TLS/SSL, ensuring confidentiality and integrity. Since HTTPS is a universally supported and standard security practice, there is no technical justification for relying on plain HTTP for any part of a modern application that handles user data or requires trust.
Real-world impact

Real-world CVEs caused by CWE-1428

No public CVE references are linked to this CWE in MITRE's catalog yet.

How attackers exploit it

Step-by-step attacker path

  1. 1

    Identify a code path that handles untrusted input without validation.

  2. 2

    Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.

  3. 3

    Deliver the payload through a normal request and observe the application's reaction.

  4. 4

    Iterate until the response leaks data, executes attacker code, or escalates privileges.

Vulnerable code example

Vulnerable pseudo

MITRE has not published a code example for this CWE. The pattern below is illustrative — see Resources for canonical references.

Vulnerable pseudo 
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}
Secure code example

Secure pseudo

Secure pseudo 
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist

How to prevent CWE-1428

  • Architecture and Design Explicitly require HTTPS or another mechanism that ensures that communication is encrypted [REF-1464].
  • Implementation Avoid using "mixed content," i.e., serving a web page over HTTPS in which the page includes elements that use "http:" URLs [REF-1466] [REF-1467]. This is often done for images or other resources that do not seem to have privacy or security implications.
  • Implementation / Operation Perform "HTTPS forcing," that is, redirecting HTTP requests to HTTPS.
  • Operation If the product supports multiple protocols, ensure that encrypted protocols (such as HTTPS) are required, and remove any unencrypted protocols (such as HTTP).
Detection signals

How to detect CWE-1428

SAST High

Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.

DAST Moderate

Run dynamic application security testing against the live endpoint.

Runtime Moderate

Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.

Code review Moderate

Code review: flag any new code that handles input from this surface without using the validated framework helpers.

Plexicus auto-fix

Plexicus auto-detects CWE-1428 and opens a fix PR in under 60 seconds.

Codex Remedium scans every commit, identifies this exact weakness, and ships a reviewer-ready pull request with the patch. No tickets. No hand-offs.

Get a demo Try Plexicus free
Frequently asked questions

Frequently asked questions

What is CWE-1428?

This vulnerability occurs when an application uses unencrypted HTTP connections instead of the secure HTTPS alternative, even when HTTPS is available.

How serious is CWE-1428?

MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.

What languages or platforms are affected by CWE-1428?

MITRE lists the following affected platforms: Not OS-Specific, Not Architecture-Specific, Not Technology-Specific.

How can I prevent CWE-1428?

Explicitly require HTTPS or another mechanism that ensures that communication is encrypted [REF-1464]. Avoid using "mixed content," i.e., serving a web page over HTTPS in which the page includes elements that use "http:" URLs [REF-1466] [REF-1467]. This is often done for images or other resources that do not seem to have privacy or security implications.

How does Plexicus detect and fix CWE-1428?

Plexicus's SAST engine matches the data-flow signature for CWE-1428 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.

Where can I learn more about CWE-1428?

MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/1428.html. You can also reference OWASP and NIST documentation for adjacent guidance.

Related weaknesses

Weaknesses related to CWE-1428

CWE-319 Parent

Cleartext Transmission of Sensitive Information

This vulnerability occurs when an application sends sensitive data, such as passwords or personal information, over a network connection…

CWE-5 Sibling

J2EE Misconfiguration: Data Transmission Without Encryption

This vulnerability occurs when a J2EE application transmits sensitive data, like login credentials or session tokens, across a network…

CWE-614 Sibling

Sensitive Cookie in HTTPS Session Without 'Secure' Attribute

This vulnerability occurs when a web application transmits sensitive cookies over an HTTPS connection but fails to set the 'Secure'…

Resources

Further reading

Ready when you are

Don't Let Security
Weigh You Down.

Stop choosing between AI velocity and security debt. Plexicus is the only platform that runs Vibe Coding Security and ASPM in parallel — one workflow, every codebase.

Get started free Book a demo