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

> Attackers can obtain sensitive information via improper object restrictions in Java AWT loggers, affecting Java Runtime Environment users.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Nov 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2q37-8v55-frjg

## What is CVE-2009-3880?

CVE-2009-3880 is a medium-severity vulnerability in Sun Jre, published on 9 Nov 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Abstract Window Toolkit (AWT) in Java Runtime Environment (JRE) in Sun Java SE 5.0 before Update 22 and 6 before Update 17, and OpenJDK, does not properly restrict the objects that may be sent to loggers, which allows attackers to obtain sensitive information via vectors related to the implementation of Component, KeyboardFocusManager, and DefaultKeyboardFocusManager, aka Bug Id 6664512.

Weakness: CWE-264

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

It affects 2 products.


Products: Sun Jre, Sun Openjdk.

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

Upgrade to a fixed version.

## Is CVE-2009-3880 being exploited?

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

## Other vulnerabilities in Sun Jre

- [CVE-2004-2764](https://insights.sbomify.com/CVE-2004-2764/): Information disclosure in n/a (critical 10.0)
- [CVE-2009-1671](https://insights.sbomify.com/CVE-2009-1671/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-1672](https://insights.sbomify.com/CVE-2009-1672/): Code injection in n/a (critical 9.3)
- [CVE-2005-3583](https://insights.sbomify.com/CVE-2005-3583/): Denial of service in n/a (high 7.8)
- [CVE-2009-3879](https://insights.sbomify.com/CVE-2009-3879/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-3880 is a medium-severity vulnerability in Sun Jre, published on 9 Nov 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-3880 in the wild and no public exploit code.

Affected product: Sun Jre. 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-3880/ (Markdown: https://insights.sbomify.com/CVE-2009-3880/index.md)
```

## Sources

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

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