dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2008-1195

HIGH · 9.3 CVSS v2.0 Published 2008-03-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Sun JDK and Java Runtime Environment (JRE) 6 Update 4 and earlier and 5.0 Update 14 and earlier; and SDK and JRE 1.4.2_16 and earlier; allows remote attackers to access arbitrary network services on the local host via unspecified vectors related to JavaScript and Java APIs.

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 · high confidence

This is a critical Java vulnerability (CVSS 9.3) affecting Sun JDK/JRE 6 Update 4 and earlier, 5.0 Update 14 and earlier, and SDK/JRE 1.4.2_16 and earlier. The flaw allows remote attackers to bypass Java sandbox restrictions via unspecified vectors involving JavaScript and Java API interactions, enabling access to arbitrary network services on the local host.

MitigationUpgrade Java installations to versions beyond the vulnerable releases (6 Update 5+, 5.0 Update 15+, 1.4.2_17+) to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Ubuntu LinuxOperating system
Affected:= 6.06= 6.10= 7.04= 7.10
JdkApplication
Affected:= 1.5.0= 1.6.0
JreApplication
Affected:= 1.4.2= 1.4.2_1= 1.4.2_2= 1.4.2_3= 1.4.2_4= 1.4.2_5= 1.4.2_6= 1.4.2_7= 1.4.2_8= 1.4.2_9= 1.4.2_10= 1.4.2_11
SdkApplication
Affected:= 1.4.2= 1.4.2_1= 1.4.2_2= 1.4.2_3= 1.4.2_4= 1.4.2_5= 1.4.2_6= 1.4.2_7= 1.4.2_8= 1.4.2_9= 1.4.2_10= 1.4.2_11

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Java is installed
    Run 'java -version' or 'which java' in the terminal
    Affected if No Java runtime is found, the system is not affected by this specific vulnerability
  2. Identify the installed Java version
    Run 'java -version 2>&1' and note the full version string (e.g., 1.6.0, 1.5.0, 1.4.2_XX)
    Affected if Version displays as 1.6.0, 1.5.0, or 1.4.2_XX and is equal to or lower than the vulnerable releases
  3. Verify the exact update version for JDK/JRE 6
    For Java 6, run 'java -version' and check if the build is earlier than '1.6.0_05' (Update 5 or earlier is vulnerable)
    Affected if The version shows 1.6.0 through 1.6.0_04 (Update 4 or earlier)
  4. Verify the exact update version for JDK/JRE 5.0
    For Java 5, check if the version is 1.5.0_00 through 1.5.0_14 (Update 14 or earlier is vulnerable)
    Affected if The version shows 1.5.0_14 or earlier
  5. Verify the exact update version for SDK/JRE 1.4.2
    For Java 1.4.2, check if the version is 1.4.2_16 or earlier (e.g., 1.4.2_11, 1.4.2_10, etc.)
    Affected if The version shows 1.4.2_16 or earlier
  6. Check for Java browser plugin (required attack vector)
    On Linux, check for browser plugin files in '~/.mozilla/plugins/' or '/usr/lib/mozilla/plugins/' for 'libnpjp2.so' (Java Plug-in)
    Affected if The Java browser plugin exists and the Java version is in the vulnerable range listed above

The system is affected if Java is installed with a version at or below 1.6.0_04, 1.5.0_14, or 1.4.2_16 and the Java browser plugin is present, allowing malicious applets to bypass sandbox restrictions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Java installations to versions beyond the vulnerable releases (6 Update 5+, 5.0 Update 15+, 1.4.2_17+) to remediate this vulnerability.

Recommended fix Moderate confidence

JDK/JRE 6 Update 5 or later; JDK 5.0 Update 15 or later; SDK/JRE 1.4.2_17 or later

  1. 1. Identify the currently installed Java version by running 'java -version' or checking the Ubuntu package management system
  2. 2. For Ubuntu 6.06/6.10/7.04/7.10: Update the package repositories with 'sudo apt-get update'
  3. 3. Remove the vulnerable Java installation using the appropriate package manager command
  4. 4. Install the fixed Java version from Ubuntu's repositories or upgrade to a newer Ubuntu release that ships with patched Java
  5. 5. Verify the new Java version is installed correctly by running 'java -version'
  6. 6. Ensure any applications using Java are restarted to use the updated runtime
Caveat Older Java applications may have compatibility issues with newer Java versions; some legacy functionality may require testing

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

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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