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.)
CWE-614 Variante Rascunho
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.
Definição
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.
Impacto no mundo real
Real-world CVEs caused by CWE-614
-
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.
-
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.
-
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.
-
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.
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 1
Identificar um caminho de código que trata input não confiável sem validação.
- 2
Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.
- 3
Entregar o payload através de um pedido normal e observar a reação da aplicação.
- 4
Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.
Exemplo de código vulnerável
Vulnerable Java
The snippet of code below, taken from a servlet doPost() method, sets an accountID cookie (sensitive) without calling setSecure(true).
Cookie c = new Cookie(ACCOUNT_ID, acctID);
response.addCookie(c); Exemplo de código seguro
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.
Lista de verificação de prevenção
How to prevent CWE-614
- Implementation Always set the secure attribute when the cookie should be sent via HTTPS only.
Sinais de deteção
How to detect CWE-614
CWE-614
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Perguntas frequentes O que é o CWE-614?
Qual a gravidade do CWE-614?
Que linguagens ou plataformas são afetadas pelo CWE-614?
Como posso prevenir o CWE-614?
Como é que o Plexicus deteta e corrige o CWE-614?
Onde posso saber mais sobre o CWE-614?
Frequently asked questions
O que é o 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.
Qual a gravidade do CWE-614?
A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.
Que linguagens ou plataformas são afetadas pelo CWE-614?
MITRE lists the following affected platforms: Web Based.
Como posso prevenir o CWE-614?
Always set the secure attribute when the cookie should be sent via HTTPS only.
Como é que o Plexicus deteta e corrige o CWE-614?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-614 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.
Onde posso saber mais sobre o CWE-614?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/614.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-614
CWE-319 Pai
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 Irmão
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 Irmão
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…
Pronto para validar o que importa?
Pronto para validar o que importa.
O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.