# CVE-2009-2672: Information disclosure in n/a

> Untrusted Java applets can access browser cookies, allowing remote attackers to hijack web sessions. Users should upgrade their Java Runtime Environment.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 5 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-fj22-5g9h-44w5

## What is CVE-2009-2672?

CVE-2009-2672 is a high-severity vulnerability in Sun Jdk, published on 5 Aug 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The proxy mechanism implementation in Sun Java Runtime Environment (JRE) in JDK and JRE 6 before Update 15, and JDK and JRE 5.0 before Update 20, does not prevent access to browser cookies by untrusted (1) applets and (2) Java Web Start applications, which allows remote attackers to hijack web sessions via unspecified vectors.

Weakness: CWE-264

## Which versions are affected by CVE-2009-2672?

It affects 2 products.


Products: Sun Jdk, Sun Jre.

## How do I fix CVE-2009-2672?

Upgrade to a fixed version.

## Is CVE-2009-2672 being exploited?

There is no known exploitation of CVE-2009-2672 in the wild and no public exploit code.

## Other vulnerabilities in Sun Jdk

- [CVE-2011-3521](https://insights.sbomify.com/CVE-2011-3521/): Deserialization in n/a (critical 10.0)
- [CVE-2011-3548](https://insights.sbomify.com/CVE-2011-3548/): Other in n/a (critical 10.0)
- [CVE-2011-3549](https://insights.sbomify.com/CVE-2011-3549/): Other in n/a (critical 10.0)
- [CVE-2011-3554](https://insights.sbomify.com/CVE-2011-3554/): Other in n/a (critical 10.0)
- [CVE-2011-0802](https://insights.sbomify.com/CVE-2011-0802/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-2672 and fix it if it is affected.

What it is: CVE-2009-2672 is a high-severity vulnerability in Sun Jdk, published on 5 Aug 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2009-2672 in the wild and no public exploit code.

Affected product: Sun Jdk. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2009-2672/ (Markdown: https://insights.sbomify.com/CVE-2009-2672/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2009-2672
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2009-2672
- OSV: https://osv.dev/vulnerability/CVE-2009-2672

---
From sbomify Insights: https://insights.sbomify.com/CVE-2009-2672/
Summaries are generated and may contain mistakes; the official description above is the record.