CWE-1275 Variant Incomplete Medium likelihood

Sensitive Cookie with Improper SameSite Attribute

This vulnerability occurs when a sensitive cookie does not have a secure SameSite attribute configured, leaving it exposed to cross-site request forgery (CSRF) attacks.

Definition

What is CWE-1275?

This vulnerability occurs when a sensitive cookie does not have a secure SameSite attribute configured, leaving it exposed to cross-site request forgery (CSRF) attacks.

The SameSite cookie attribute is a critical browser security feature that controls whether a cookie is sent with cross-site requests. It has three possible values: 'Strict' (most secure, never sent cross-site), 'Lax' (sent with safe top-level navigation like links), and 'None' (always sent, requiring the Secure flag). When this attribute is omitted or set insecurely for sensitive cookies—like session or authentication tokens—those credentials can be automatically included in malicious cross-site requests, bypassing the browser's default protections. This creates a direct path for CSRF attacks, where an attacker's site can trigger authenticated actions on the target site without the user's consent. While other defenses like anti-CSRF tokens are important, properly configuring SameSite provides a fundamental, browser-enforced layer of security. For maximum protection, set sensitive cookies to 'Strict' or 'Lax' unless a specific cross-site functionality requires 'None', in which case the Secure flag is mandatory.

Auswirkungen in der Praxis

Real-world CVEs caused by CWE-1275

CVE-2022-24045

Web application for a room automation system has client-side JavaScript that sets a sensitive cookie without the SameSite security attribute, allowing the cookie to be sniffed

Wie Angreifer es ausnutzen

Angreiferpfad Schritt für Schritt

1
In this example, a cookie is used to store a session ID for a client's interaction with a website. The snippet of code below establishes a new cookie to hold the sessionID.
2
Since the sameSite attribute is not specified, the cookie will be sent to the website with each request made by the client. An attacker can potentially perform a CSRF attack by using the following malicious page:
3
When the client visits this malicious web page, it submits a '/setEmail' POST HTTP request to the vulnerable website. Since the browser automatically appends the 'sessionid' cookie to the request, the website automatically performs a 'setEmail' action on behalf of the client.
4
To mitigate the risk, use the sameSite attribute of the 'sessionid' cookie set to 'Strict'.

Verwundbares Codebeispiel

Vulnerable JavaScript

In this example, a cookie is used to store a session ID for a client's interaction with a website. The snippet of code below establishes a new cookie to hold the sessionID.

Verwundbar JavaScript

let sessionId = generateSessionId()
 let cookieOptions = { domain: 'example.com' }
 response.cookie('sessionid', sessionId, cookieOptions)

Angreifer-Payload

Since the sameSite attribute is not specified, the cookie will be sent to the website with each request made by the client. An attacker can potentially perform a CSRF attack by using the following malicious page:

Angreifer-Payload HTML

<html>

```
   <form id=evil action="http://local:3002/setEmail" method="POST">
  	 <input type="hidden" name="newEmail" value="abc@example.com" />
   </form>
 <script>evil.submit()</script>
 </html>

Sicheres Codebeispiel

Secure JavaScript

To mitigate the risk, use the sameSite attribute of the 'sessionid' cookie set to 'Strict'.

Sicher JavaScript

let sessionId = generateSessionId()
 let cookieOptions = { domain: 'example.com', sameSite: 'Strict' }
 response.cookie('sessionid', sessionId, cookieOptions)

What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.

Präventions-Checkliste

How to prevent CWE-1275

Implementation Set the SameSite attribute of a sensitive cookie to 'Lax' or 'Strict'. This instructs the browser to apply this cookie only to same-domain requests, which provides a good Defense in Depth against CSRF attacks. When the 'Lax' value is in use, cookies are also sent for top-level cross-domain navigation via HTTP GET, HEAD, OPTIONS, and TRACE methods, but not for other HTTP methods that are more like to cause side-effects of state mutation.

Erkennungssignale

How to detect CWE-1275

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.)

CWE-1275

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.

Request AI Swarm Pentest

Häufig gestellte Fragen

Frequently asked questions

Was ist CWE-1275?

This vulnerability occurs when a sensitive cookie does not have a secure SameSite attribute configured, leaving it exposed to cross-site request forgery (CSRF) attacks.

Wie gravierend ist CWE-1275?

MITRE stuft die Exploit-Wahrscheinlichkeit als mittel ein — eine Ausnutzung ist realistisch, erfordert aber meist bestimmte Bedingungen.

Welche Sprachen oder Plattformen sind von CWE-1275 betroffen?

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

Wie kann ich CWE-1275 verhindern?

Set the SameSite attribute of a sensitive cookie to 'Lax' or 'Strict'. This instructs the browser to apply this cookie only to same-domain requests, which provides a good Defense in Depth against CSRF attacks. When the 'Lax' value is in use, cookies are also sent for top-level cross-domain navigation via HTTP GET, HEAD, OPTIONS, and TRACE methods, but not for other HTTP methods that are more like to cause side-effects of state mutation.

Wie erkennt und behebt Plexicus CWE-1275?

Die SAST-Engine von Plexicus erkennt die Datenfluss-Signatur von CWE-1275 bei jedem Commit. Bei einem Treffer öffnet unser Codex-Remedium-Agent einen Fix-PR mit korrigiertem Code, Tests und einer einzeiligen Zusammenfassung für den Reviewer.

Wo erfahre ich mehr über CWE-1275?

MITRE veröffentlicht die kanonische Definition unter https://cwe.mitre.org/data/definitions/1275.html. Für ergänzende Hinweise kannst du auch die OWASP- und NIST-Dokumentation heranziehen.

Verwandte Schwachstellen

Weaknesses related to CWE-1275

CWE-923 Parent

Bereit zu validieren, was zählt.

Plexicus ist Proof-Driven AppSec: validierte Funde, kontextuelles Verständnis und geprüfte Remediation — in Evidenz verankert, mit Ihnen gescoped.

Pentest buchen

Sensitive Cookie with Improper SameSite Attribute

What is CWE-1275?

Real-world CVEs caused by CWE-1275

Angreiferpfad Schritt für Schritt

Vulnerable JavaScript

Secure JavaScript

How to prevent CWE-1275

How to detect CWE-1275

Don't catalog this weakness. Prove it's reachable.

Frequently asked questions

Weaknesses related to CWE-1275

Improper Restriction of Communication Channel to Intended Endpoints

Reliance on IP Address for Authentication

Improper Validation of Certificate with Host Mismatch

Channel Accessible by Non-Endpoint

Unprotected Primary Channel

Unprotected Alternate Channel

Improper Verification of Source of a Communication Channel

Incorrectly Specified Destination in a Communication Channel

Permissive Cross-domain Security Policy with Untrusted Domains

Further reading

Bereit zu validieren, was zählt.

Prüfen Sie, ob AI Swarm Pentest zu Ihrer Umgebung passt.

Anfrage erhalten. Nächsten Schritt buchen.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`