dbcve.org
JdkApplication · Sun

CVE-2009-1094

HIGH · 10.0 CVSS v2.0 Published 2009-03-25
Fix available
A fix is available. Upgrade to after 1.6.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unspecified vulnerability in the LDAP implementation in Java SE Development Kit (JDK) and Java Runtime Environment (JRE) 5.0 Update 17 and earlier; 6 Update 12 and earlier; SDK and JRE 1.3.1_24 and earlier; and 1.4.2_19 and earlier allows remote LDAP servers to execute arbitrary code via unknown vectors related to serialized data.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JdkApplication
Affected:<= 1.5.0<= 1.6.0= 1.5.0= 1.6.0
JreApplication
Affected:<= 1.5.0<= 1.6.0= 1.5.0= 1.6.0<= 1.3.1_24= 1.3.1= 1.3.1_01= 1.3.1_2= 1.3.1_03= 1.3.1_04= 1.3.1_05= 1.3.1_06
SdkApplication
Affected:<= 1.3.1_24= 1.3.1= 1.3.1_01= 1.3.1_01a= 1.3.1_02= 1.3.1_03= 1.3.1_04= 1.3.1_05= 1.3.1_06= 1.3.1_07= 1.3.1_08= 1.3.1_09

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.6.0
Vendor patch sunsolve.sun.com →
Recommended fix High confidence

Upgrade to Java 6 Update 13 or later (for 1.6.x users), Java 5.0 Update 18 or later (for 1.5.x users), Java 1.4.2_20 or later (for 1.4.x users), or Java 1.3.1_25 or later (for 1.3.x users). Consider migrating to a currently supported Java LTS release such as Java 8, 11, 17, or 21 for long-term secur

  1. 1. Identify the current Java/JRE/JDK version installed by running 'java -version' or checking the JRE/JDK installation directory.
  2. 2. For Java 6 (1.6.0) users: Upgrade to Java 6 Update 13 or later, which contains the fix for this vulnerability.
  3. 3. For Java 5.0 (1.5.0) users: Upgrade to Java 5.0 Update 18 or later, which contains the fix for this vulnerability.
  4. 4. For Java 1.4.2 users: Upgrade to Java 1.4.2_20 or later, which contains the fix for this vulnerability.
  5. 5. For Java 1.3.1 users: Upgrade to Java 1.3.1_25 or later, which contains the fix for this vulnerability.
  6. 6. After upgrading, verify the new version by running 'java -version' and confirm it is beyond the vulnerable versions listed.
  7. 7. Test all Java applications to ensure compatibility with the new Java version.
Caveat Legacy applications built for Java 1.3.1, 1.4.2, or early 5.0/6.0 versions may have compatibility issues with newer Java releases due to API changes, deprecated features, or removed libraries. Thorough testing is recommended before deploying the upgrade to production environments.

Generated from the published advisory — verify against the referenced sources before acting.

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2009-1094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2009-1094 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data