dbcve.org
JdkApplication · Sun

CVE-2006-6731

HIGH · 9.3 CVSS v2.0 Published 2006-12-26
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
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
Multiple buffer overflows in Sun Java Development Kit (JDK) and Java Runtime Environment (JRE) 5.0 Update 7 and earlier, Java System Development Kit (SDK) and JRE 1.4.2_12 and earlier 1.4.x versions, and SDK and JRE 1.3.1_18 and earlier allow attackers to develop Java applets that read, write, or execute local files, possibly related to (1) integer overflows in the Java_sun_awt_image_ImagingLib_convolveBI, awt_parseRaster, and awt_parseColorModel functions; (2) a stack overflow in the Java_sun_awt_image_ImagingLib_lookupByteRaster function; and (3) improper handling of certain negative values in the Java_sun_font_SunLayoutEngine_nativeLayout function. NOTE: some of these details are obtained from third party information.

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
JreApplication
Affected:= 1.3.1= 1.3.1_2= 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= 1.3.1_10= 1.3.1_11= 1.3.1_12
SdkApplication
Affected:= 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= 1.3.1_10

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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
Patch available Apply the vendor patch
Vendor patch www.securityfocus.com →
Recommended fix High confidence

Current supported LTS Java versions (OpenJDK 11+, OpenJDK 17+, or Oracle JDK 11+)

  1. 1. Identify all systems running the affected Java versions (JDK/JRE 1.5.0, 1.4.2_12 and earlier, 1.3.1_18 and earlier)
  2. 2. Determine the current Java usage requirements for your applications to select an appropriate modern JRE/JDK
  3. 3. Download and install a current, supported Long-Term Support (LTS) Java version such as OpenJDK 11 LTS, OpenJDK 17 LTS, or Oracle JDK 17 from https://adoptium.net/ or https://www.oracle.com/java/technologies/downloads/
  4. 4. Update all application startup scripts, environment variables (JAVA_HOME, PATH), and build configurations to reference the new Java installation
  5. 5. Test all Java-based applications to ensure compatibility with the new Java version
  6. 6. Remove or secure access to the old vulnerable Java installations
  7. 7. Verify the new Java version is active by running 'java -version'
Caveat Applications written for Java 1.3.1/1.5.0 may require code changes to run on modern Java versions due to API removals and language specification changes; thorough testing is required

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

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-6731 — 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-2006-6731 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