CWE-614 Variante Borrador

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' attribute on those cookies.

Definición

What is CWE-614?

This vulnerability occurs when a web application transmits sensitive cookies over an HTTPS connection but fails to set the 'Secure' attribute on those cookies.
When a cookie is marked with the 'Secure' attribute, browsers guarantee it will only be sent over encrypted HTTPS connections. If this attribute is missing, even if the application initially uses HTTPS, the browser may inadvertently send the sensitive cookie over an unencrypted HTTP request. This often happens during redirects, when loading mixed content, or if a user manually types an HTTP URL, exposing session tokens or authentication data to interception. To prevent this, developers must explicitly set the 'Secure' flag for all cookies containing sensitive information in their application code. This is a critical server-side configuration that should be part of a standard secure cookie policy, alongside other attributes like 'HttpOnly' and 'SameSite'. Relying solely on HTTPS for the initial transmission is not sufficient; the 'Secure' attribute provides an essential enforcement layer at the browser level.
Vulnerability Diagram CWE-614
Cookie Without Secure Flag Browser cookie: session=… Connection Set-Cookie: session=abc (no Secure flag) (no HttpOnly) later: HTTP image src=… → cookie attached on http:// MITM on Wi-Fi steals session Without Secure, browsers send the cookie on plain HTTP — sniffable.
Impacto en el mundo real

Real-world CVEs caused by CWE-614

  • CVE-2004-0462

    A product does not set the Secure attribute for sensitive cookies in HTTPS sessions, which could cause the user agent to send those cookies in plaintext over an HTTP session with the product.

  • CVE-2008-3663

    A product does not set the secure flag for the session cookie in an https session, which can cause the cookie to be sent in http requests and make it easier for remote attackers to capture this cookie.

  • CVE-2008-3662

    A product does not set the secure flag for the session cookie in an https session, which can cause the cookie to be sent in http requests and make it easier for remote attackers to capture this cookie.

  • CVE-2008-0128

    A product does not set the secure flag for a cookie in an https session, which can cause the cookie to be sent in http requests and make it easier for remote attackers to capture this cookie.

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

  1. 1

    Identifica una ruta de código que maneje entrada no confiable sin validación.

  2. 2

    Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.

  3. 3

    Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.

  4. 4

    Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.

Ejemplo de código vulnerable

Vulnerable Java

The snippet of code below, taken from a servlet doPost() method, sets an accountID cookie (sensitive) without calling setSecure(true).

Vulnerable Java 
Cookie c = new Cookie(ACCOUNT_ID, acctID);
  response.addCookie(c);
Ejemplo de código seguro

Secure pseudo

Seguro 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.
Lista de prevención

How to prevent CWE-614

  • Implementation Always set the secure attribute when the cookie should be sent via HTTPS only.
Señales de detección

How to detect CWE-614

Automated Static Analysis High

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Auto-corrección de Plexicus

Plexicus detecta automáticamente CWE-614 y abre un PR de corrección en menos de 60 segundos.

Codex Remedium escanea cada commit, identifica esta debilidad concreta y entrega un pull request listo para revisión con el parche. Sin tickets. Sin traspasos.

Solicitar demo Probar Plexicus gratis
Preguntas frecuentes

Frequently asked questions

¿Qué es CWE-614?

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

¿Qué gravedad tiene CWE-614?

MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.

¿Qué lenguajes o plataformas se ven afectados por CWE-614?

MITRE lists the following affected platforms: Web Based.

¿Cómo puedo prevenir CWE-614?

Always set the secure attribute when the cookie should be sent via HTTPS only.

¿Cómo detecta y corrige Plexicus CWE-614?

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-614 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.

¿Dónde puedo aprender más sobre CWE-614?

MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/614.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.

Debilidades relacionadas

Weaknesses related to CWE-614

CWE-319 Padre

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-1428 Hermano

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…

CWE-5 Hermano

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…

Recursos

Further reading

Listo cuando tú lo estés

Deja de pagar por desarrollador.
Empieza a cerrar el bucle.

Plexicus es el ASPM nativo de IA que escanea, filtra, corrige, pentestea y explica — de forma autónoma. Desarrolladores ilimitados, repos ilimitados, acciones de IA de uso justo. Nivel gratuito real, €269/mo anual cuando estés listo.

Comenzar gratis Reservar una demo