CVE-2006-6737 json
Unspecified vulnerability in Sun Java Development Kit (JDK) and Java Runtime Environment (JRE) 5.0 Update 5 and earlier, Java System Develo…
published 2006-12-26 19 y ago modified 2026-06-16 4 mo ago also EUVD-2006-6720
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in Sun Java Development Kit (JDK) and Java Runtime Environment (JRE) 5.0 Update 5 and earlier, Java System Development Kit (SDK) and JRE 1.4.2_10 and earlier 1.4.x versions, and SDK and JRE 1.3.1_18 and earlier allows attackers to use untrusted applets to "access data in other applets," aka "The first issue."
Patch / fix
- java-1.5.0-ibm RHEL 4 EXTRAS 1:1.5.0.3-1jpp.3.el4
- java-1.5.0-ibm-src RHEL 4 EXTRAS 1:1.5.0.3-1jpp.3.el4
- java-1.5.0-ibm-demo RHEL 4 EXTRAS 1:1.5.0.3-1jpp.3.el4
- java-1.5.0-ibm-jdbc RHEL 4 EXTRAS 1:1.5.0.3-1jpp.3.el4
- java-1.5.0-ibm-plugin RHEL 4 EXTRAS 1:1.5.0.3-1jpp.3.el4
- java-1.5.0-ibm-javacomm RHEL 4 EXTRAS 1:1.5.0.3-1jpp.3.el4
- IBMJava2-JRE RHEL 2.1 1:1.3.1-12
- IBMJava2-SDK RHEL 2.1 1:1.3.1-11
red hat advisories RHSA-2007:0073RHSA-2007:0072RHSA-2007:0062
- securityfocus.com/bid/21674 advisory
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2006-6737 updated
security flaw
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.45% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
References
-
securityfocus.com
/bid/21674
vdb-entry, patch, third-party-advisory
-
redhat.com
/support/errata/RHSA-2007-0062.html
vendor-advisory, third-party-advisory
-
novell.com
/linux/security/advisories/2007_45_java.html
vendor-advisory, third-party-advisory
-
lists.suse.com
/archive/suse-security-announce/2007-Jan/0003.html
vendor-advisory, mailing-list, third-party-advisory
-
novell.com
/linux/security/advisories/2007_10_ibmjava.html
vendor-advisory, third-party-advisory
-
redhat.com
/support/errata/RHSA-2007-0072.html
vendor-advisory, third-party-advisory
-
redhat.com
/support/errata/RHSA-2007-0073.html
vendor-advisory, third-party-advisory, vdb-entry
-
gentoo.org
/security/en/glsa/glsa-200705-20.xml
vendor-advisory, third-party-advisory
-
security.gentoo.org
/glsa/glsa-200702-08.xml
vendor-advisory, third-party-advisory
-
sunsolve.sun.com
/search/document.do?assetkey=1-26-102732-1
vendor-advisory, broken-link
-
security.gentoo.org
/glsa/glsa-200701-15.xml
vendor-advisory, third-party-advisory
-
secunia.com
/advisories/26049
third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11087
vdb-entry, signature, third-party-advisory
-
secunia.com
/advisories/24099
third-party-advisory
-
secunia.com
/advisories/25404
third-party-advisory
-
securitytracker.com
/id?1017427
vdb-entry, third-party-advisory
-
secunia.com
/advisories/24189
third-party-advisory
-
vupen.com
/english/advisories/2006/5075
vdb-entry, permissions-required
-
support.novell.com
/techcenter/psdb/4f850d1e2b871db609de64ec70f0089c.html
third-party-advisory
-
secunia.com
/advisories/26119
third-party-advisory
-
secunia.com
/advisories/23650
third-party-advisory
-
secunia.com
/advisories/23835
third-party-advisory
-
secunia.com
/advisories/23398
third-party-advisory
-
support.novell.com
/techcenter/psdb/d2f549cc040cd81ae4a268bb5edfe918.html
third-party-advisory
Sources
- CVE List CVE-2006-6737
- NVD CVE-2006-6737
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.