# What is CVE-2009-3873?

> CVE-2009-3873 is a critical-severity flaw (CVSS 9.3) in JDK from Sun, published on 5 November 2009. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 4.2%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2009-3873

## At a glance

- **Verdict:** Fix this soon. Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
- **Precursor Intelligence risk score:** 54 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes.
- **Severity:** Critical (CVSS 9.3 out of 10)
- **Known to be exploited:** No, not on the list of flaws known to be exploited today
- **Chance of use in the next 30 days:** 4.2% (latest exploit-likelihood forecast)
- **Published:** 5 November 2009
- **Record last updated:** 16 June 2026
- **Main product:** JDK from Sun
- **Affected products:** 3

## What is CVE-2009-3873? In plain terms

It can be attacked from anywhere on the internet without logging in. If it works, the attacker can read data, change data and take it offline.

### The official description

The JPEG Image Writer in Sun Java SE in JDK and JRE 5.0 before Update 22, JDK and JRE 6 before Update 17, and SDK and JRE 1.4.x before 1.4.2_24 allows remote attackers to gain privileges via a crafted image file, related to a "quantization problem," aka Bug Id 6862968.

### What kind of flaw is it?

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

### How an attack on it works

- Where an attacker can be: Anywhere on the internet
- How hard it is to pull off: Some conditions needed
- Login needed first: No login needed
- What an attacker gets: Can read data, change data and take it offline

Severity vector: `AV:N/AC:M/Au:N/C:C/I:C/A:C`

## Is CVE-2009-3873 being exploited? Not that we know of

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 4.2%. That can change at any time, which is why we keep watching.

Exploit likelihood over the last 7 days: 4.2%, 4.2%, 4.2%, 4.2%, 4.2%, 4.2%, 4.2%.

### Timeline

- 5 November 2009: Published
- 16 June 2026: Record last updated

### How Precursor Intelligence ranks it

CVE-2009-3873 scores **54 out of 100 (Medium)**, with the action "Plan remediation".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2009-3873?

The published record lists 3 products.

- [JDK](https://www.precursorintelligence.com/product/sun/jdk) by [Sun](https://www.precursorintelligence.com/vendors/sun) (Application): 1.5.0-update_1, 1.5.0-update_2, 1.5.0-update_3, 1.5.0-update_4, 1.5.0-update_5, 1.5.0-update_6, 1.5.0-update_7, 1.5.0-update_8, 1.5.0-update_9, 1.5.0-update_10, 1.5.0-update_11, 1.5.0-update_12, 1.5.0-update_13, 1.5.0-update_14, 1.5.0-update_15, 1.5.0-update_16, 1.5.0-update_17, 1.5.0-update_18, 1.5.0-update_19, 1.5.0-update_20, 1.5.0-update_21, 1.6.0-update_1, 1.6.0-update2, 1.6.0-update_3, 1.6.0-update_4, 1.6.0-update_5, 1.6.0-update_6, 1.6.0-update_7, 1.6.0-update_8, 1.6.0-update_9, 1.6.0-update_10, 1.6.0-update_11, 1.6.0-update_12, 1.6.0-update_13, 1.6.0-update_14, 1.6.0-update_15, 1.6.0-update_16
- [JRE](https://www.precursorintelligence.com/product/sun/jre) by [Sun](https://www.precursorintelligence.com/vendors/sun) (Application): 1.3.1_01a, 1.3.1_1, 1.3.1_01, 1.3.1_02, 1.3.1_2, 1.3.1_03, 1.3.1_3, 1.3.1_4, 1.3.1_04, 1.3.1_05, 1.3.1_5, 1.3.1_06, 1.3.1_6, 1.3.1_07, 1.3.1_7, 1.3.1_8, 1.3.1_08, 1.3.1_9, 1.3.1_09, 1.3.1_10, 1.3.1_11, 1.3.1_12, 1.3.1_13, 1.3.1_14, 1.3.1_15, 1.3.1_16, 1.3.1_17, 1.3.1_18, 1.3.1_19, 1.3.1_20, 1.3.1_21, 1.3.1_22, 1.3.1_23, 1.3.1_24, 1.3.1_25, 1.4.2_1, 1.4.2_01, 1.4.2_2, 1.4.2_02, 1.4.2_03 and 62 more
- [SDK](https://www.precursorintelligence.com/product/sun/sdk) by [Sun](https://www.precursorintelligence.com/vendors/sun) (Application): 1.3.1_01a, 1.3.1_01, 1.3.1_2, 1.3.1_02, 1.3.1_03, 1.3.1_3, 1.3.1_4, 1.3.1_04, 1.3.1_5, 1.3.1_05, 1.3.1_6, 1.3.1_06, 1.3.1_7, 1.3.1_07, 1.3.1_8, 1.3.1_08, 1.3.1_9, 1.3.1_09, 1.3.1_10, 1.3.1_11, 1.3.1_12, 1.3.1_13, 1.3.1_14, 1.3.1_15, 1.3.1_16, 1.3.1_17, 1.3.1_18, 1.3.1_19, 1.3.1_20, 1.3.1_21, 1.3.1_22, 1.3.1_23, 1.3.1_24, 1.3.1_25, 1.4.2_01, 1.4.2_1, 1.4.2_2, 1.4.2_02, 1.4.2_03, 1.4.2_3 and 25 more

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

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

### References

- [sunsolve.sun.com](http://sunsolve.sun.com/search/document.do?assetkey=1-66-270474-1) (Patch, Vendor advisory)
- [java.sun.com](http://java.sun.com/javase/6/webnotes/6u17.html) (Vendor advisory)
- [secunia.com](http://secunia.com/advisories/37231) (Vendor advisory)
- [vupen.com](http://www.vupen.com/english/advisories/2009/3131) (Vendor advisory)
- [lists.apple.com](http://lists.apple.com/archives/security-announce/2009/Dec/msg00000.html)
- [lists.apple.com](http://lists.apple.com/archives/security-announce/2009/Dec/msg00001.html)
- [lists.opensuse.org](http://lists.opensuse.org/opensuse-security-announce/2009-11/msg00010.html)
- [marc.info](http://marc.info/?l=bugtraq&m=126566824131534&w=2)
- [marc.info](http://marc.info/?l=bugtraq&m=131593453929393&w=2)
- [marc.info](http://marc.info/?l=bugtraq&m=134254866602253&w=2)
- [secunia.com](http://secunia.com/advisories/37239)
- [secunia.com](http://secunia.com/advisories/37386)
- [secunia.com](http://secunia.com/advisories/37581)
- [secunia.com](http://secunia.com/advisories/37841)
- [security.gentoo.org](http://security.gentoo.org/glsa/glsa-200911-02.xml)
- [securitytracker.com](http://securitytracker.com/id?1023132)
- [support.apple.com](http://support.apple.com/kb/HT3969)
- [support.apple.com](http://support.apple.com/kb/HT3970)
- [mandriva.com](http://www.mandriva.com/security/advisories?name=MDVSA-2010:084)
- [oracle.com](http://www.oracle.com/technetwork/topics/security/cpujan2010-084891.html)
- [redhat.com](http://www.redhat.com/support/errata/RHSA-2009-1694.html)
- [securityfocus.com](http://www.securityfocus.com/bid/36881)
- [oval.cisecurity.org](https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11746)
- [oval.cisecurity.org](https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6970)
- [oval.cisecurity.org](https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A8396)
- [oval.cisecurity.org](https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9602)

## Questions

### What is CVE-2009-3873?

CVE-2009-3873 is a critical-severity flaw in JDK from Sun, published on 5 November 2009. It can be attacked from anywhere on the internet without logging in. If it works, the attacker can read data, change data and take it offline.

### How serious is CVE-2009-3873?

It scores 9.3 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2009-3873 is 54 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.

### Is CVE-2009-3873 being exploited?

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 4.2%. That can change at any time, which is why we keep watching.

### Which versions does CVE-2009-3873 affect?

For JDK from Sun: 1.5.0-update_1, 1.5.0-update_2, 1.5.0-update_3, 1.5.0-update_4, 1.5.0-update_5, 1.5.0-update_6 and 31 more. The record lists 3 products in all, each with its versions, under "Who is affected" on this page.

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

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

## Does CVE-2009-3873 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact