# CVE-2009-1671: Memory corruption in n/a

> Remote attackers can execute arbitrary code via buffer overflows in the Java Deployment Toolkit ActiveX control, requiring user interaction to visit a malicious site.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **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:** No
- **Published:** 18 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-53vx-h8fh-xhg5

## What is CVE-2009-1671?

CVE-2009-1671 is a critical memory corruption vulnerability in Sun Jre, published on 18 May 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

Multiple buffer overflows in the Deployment Toolkit ActiveX control in deploytk.dll 6.0.130.3 in Sun Java SE Runtime Environment (aka JRE) 6 Update 13 allow remote attackers to execute arbitrary code via a long string argument to the (1) setInstallerType, (2) setAdditionalPackages, (3) compareVersion, (4) getStaticCLSID, or (5) launch method.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Sun Jre.

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

No fix has been published for CVE-2009-1671 yet. Limit exposure of the affected software until one is available.

## Is CVE-2009-1671 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1671 exists.

Public exploit code:

- Java SE Runtime Environment JRE 6 Update 13 - Multiple Vulnerabilities (exploitdb)

## 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-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)
- [CVE-2009-3881](https://insights.sbomify.com/CVE-2009-3881/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1671 is a critical memory corruption vulnerability in Sun Jre, published on 18 May 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2009-1671 exists.

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-1671/ (Markdown: https://insights.sbomify.com/CVE-2009-1671/index.md)
```

## Sources

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

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