CWE-784 Variant Draft High likelihood

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 data without first confirming the cookie's authenticity or…

Definition

What is CWE-784?

Attackers can easily manipulate cookie values directly in the browser or by crafting custom client-side requests. Since the application trusts this data without validation, attackers can forge cookies to impersonate other users, bypass login screens, or escalate their privileges by inserting expected values. To prevent this, developers must never treat cookies as a trusted security mechanism on their own. Always validate and verify cookie integrity on the server using techniques like cryptographic signing, comparing against server-side sessions, or using secure, tamper-proof tokens instead of plain data.

Real-world impact

Real-world CVEs caused by CWE-784

CVE-2009-1549

Attacker can bypass authentication by setting a cookie to a specific value.
CVE-2009-1619

Attacker can bypass authentication and gain admin privileges by setting an "admin" cookie to 1.
CVE-2009-0864

Content management system allows admin privileges by setting a "login" cookie to "OK."
CVE-2008-5784

e-dating application allows admin privileges by setting the admin cookie to 1.
CVE-2008-6291

Web-based email list manager allows attackers to gain admin privileges by setting a login cookie to "admin."

How attackers exploit it

Step-by-step attacker path

1
The following code excerpt reads a value from a browser cookie to determine the role of the user.
2
The following code could be for a medical records application. It performs authentication by checking if a cookie has been set.
3
The programmer expects that the AuthenticateUser() check will always be applied, and the "authenticated" cookie will only be set when authentication succeeds. The programmer even diligently specifies a 2-hour expiration for the cookie.
4
However, the attacker can set the "authenticated" cookie to a non-zero value such as 1. As a result, the $auth variable is 1, and the AuthenticateUser() check is not even performed. The attacker has bypassed the authentication.
5
In the following example, an authentication flag is read from a browser cookie, thus allowing for external control of user state data.

Vulnerable code example

Vulnerable Java

The following code excerpt reads a value from a browser cookie to determine the role of the user.

Vulnerable Java

Cookie[] cookies = request.getCookies();
  for (int i =0; i< cookies.length; i++) {
  	Cookie c = cookies[i];
  	if (c.getName().equals("role")) {
  		userRole = c.getValue();
  	}
  }

Secure code example

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-784

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.

Detection signals

How to detect CWE-784

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-784 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

What is CWE-784?

How serious is CWE-784?

MITRE rates the likelihood of exploit as High — this weakness is actively exploited in the wild and should be prioritized for remediation.

What languages or platforms are affected by CWE-784?

MITRE lists the following affected platforms: Web Based.

How can I prevent CWE-784?

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.

How does Plexicus detect and fix CWE-784?

Plexicus's SAST engine matches the data-flow signature for CWE-784 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-784?

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

Related weaknesses

Weaknesses related to CWE-784

CWE-565 Parent