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-565 Base Incompleto
Reliance on Cookies without Validation and Integrity Checking
This vulnerability occurs when an application uses cookies to make security decisions—like granting access or changing settings—but fails to verify that the cookie data is legitimate, unaltered, and…
Definición
What is CWE-565?
This vulnerability occurs when an application uses cookies to make security decisions—like granting access or changing settings—but fails to verify that the cookie data is legitimate, unaltered, and belongs to the current user.
Cookies are often used to store session identifiers, user preferences, or state information, but they are controlled by the client's browser. When an application blindly trusts cookie values without validating their integrity or checking if they match the authenticated user's session, attackers can forge or manipulate cookies to impersonate other users, escalate privileges, or bypass security controls.
To prevent this, developers should treat all client-side data, including cookies, as untrusted input. Implement server-side validation for any cookie used in security decisions, use cryptographically signed or encrypted cookies to prevent tampering, and bind session cookies to specific user attributes (like IP address or user agent) to detect session hijacking attempts.
Impacto en el mundo real
Real-world CVEs caused by CWE-565
-
e-dating application allows admin privileges by setting the admin cookie to 1.
Cómo lo explotan los atacantes
Ruta del atacante paso a paso
- 1
Identifica una ruta de código que maneje entrada no confiable sin validación.
- 2
Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.
- 3
Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.
- 4
Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.
Ejemplo de código vulnerable
Vulnerable Java
The following code excerpt reads a value from a browser cookie to determine the role of the user.
Cookie[] cookies = request.getCookies();
for (int i =0; i< cookies.length; i++) {
Cookie c = cookies[i];
if (c.getName().equals("role")) {
userRole = c.getValue();
}
} Ejemplo 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 prevención
How to prevent CWE-565
- Architecture and Design Avoid using cookie data for a security-related decision.
- Implementation Perform thorough input validation (i.e.: server side validation) on the cookie data if you're going to use it for a security related decision.
- Architecture and Design Add integrity checks to detect tampering.
- Architecture and Design Protect critical cookies from replay attacks, since cross-site scripting or other attacks may allow attackers to steal a strongly-encrypted cookie that also passes integrity checks. This mitigation applies to cookies that should only be valid during a single transaction or session. By enforcing timeouts, you may limit the scope of an attack. As part of your integrity check, use an unpredictable, server-side value that is not exposed to the client.
Señales de detección
How to detect CWE-565
CWE-565
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.
Preguntas frecuentes ¿Qué es CWE-565?
¿Qué gravedad tiene CWE-565?
¿Qué lenguajes o plataformas se ven afectados por CWE-565?
¿Cómo puedo prevenir CWE-565?
¿Cómo detecta y corrige Plexicus CWE-565?
¿Dónde puedo aprender más sobre CWE-565?
Frequently asked questions
¿Qué es CWE-565?
This vulnerability occurs when an application uses cookies to make security decisions—like granting access or changing settings—but fails to verify that the cookie data is legitimate, unaltered, and belongs to the current user.
¿Qué gravedad tiene CWE-565?
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-565?
MITRE no ha especificado plataformas afectadas para esta CWE — puede aplicar a la mayoría de los stacks de aplicaciones.
¿Cómo puedo prevenir CWE-565?
Avoid using cookie data for a security-related decision. Perform thorough input validation (i.e.: server side validation) on the cookie data if you're going to use it for a security related decision.
¿Cómo detecta y corrige Plexicus CWE-565?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-565 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-565?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/565.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-565
CWE-642 Padre
External Control of Critical State Data
This vulnerability occurs when an application stores security-sensitive state data in locations that unauthorized users can access and…
CWE-15 Hermano
External Control of System or Configuration Setting
This vulnerability occurs when an application allows users to directly modify critical system settings or configuration values from an…
CWE-426 Hermano
Untrusted Search Path
This vulnerability occurs when an application relies on an external search path, provided by a user or environment, to find and load…
CWE-472 Hermano
External Control of Assumed-Immutable Web Parameter
This vulnerability occurs when a web application incorrectly trusts data that appears to be fixed or hidden from the user, such as values…
CWE-73 Hermano
External Control of File Name or Path
This vulnerability occurs when an application uses unvalidated user input to construct file or directory paths for filesystem operations.
CWE-784 Hijo
Reliance on Cookies without Validation and Integrity Checking in a Security Decision
This vulnerability occurs when an application makes security decisions—like granting access or verifying identity—based solely on cookie…
¿Listo para validar lo que importa?
Listo para validar lo que importa.
Plexicus es Proof-Driven AppSec: hallazgos validados, comprensión contextual y remediación revisada — anclada en evidencia, acotada contigo.