dbcve.org
FirefoxWeb browser · Mozilla

CVE-2008-2799

HIGH · 10.0 CVSS v2.0 Published 2008-07-07
Fix available
A fix is available. Upgrade to after 2.0.0.14 or later.
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
Multiple unspecified vulnerabilities in Mozilla Firefox before 2.0.0.15, Thunderbird 2.0.0.14 and earlier, and SeaMonkey before 1.1.10 allow remote attackers to cause a denial of service (application crash) and possibly execute arbitrary code via unknown vectors related to the JavaScript engine.

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

Multiple unspecified vulnerabilities in the JavaScript engine of Mozilla Firefox before 2.0.0.15, Thunderbird 2.0.0.14 and earlier, and SeaMonkey before 1.1.10 allow remote attackers to cause denial of service (application crash) and possibly execute arbitrary code via malicious JavaScript.

MitigationUpgrade to Firefox 2.0.0.15+, Thunderbird 2.0.0.14+, or SeaMonkey 1.1.10+ respectively, or disable JavaScript in these applications as a workaround.

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
FirefoxWeb browser
Affected:<= 2.0.0.14= 2.0= 2.0.0.1= 2.0.0.2= 2.0.0.3= 2.0.0.4= 2.0.0.5= 2.0.0.6= 2.0.0.7= 2.0.0.8= 2.0.0.9= 2.0.0.10
SeamonkeyApplication
Affected:<= 1.1.9= 1.1= 1.1.2= 1.1.3= 1.1.4= 1.1.5= 1.1.6= 1.1.7= 1.1.8
ThunderbirdApplication
Affected:<= 2.0.0.14= 2.0.0.0= 2.0.0.1= 2.0.0.2= 2.0.0.3= 2.0.0.4= 2.0.0.5= 2.0.0.6= 2.0.0.8= 2.0.0.9= 2.0.0.11= 2.0.0.12

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

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. Identify installed Mozilla product
    Check for Firefox, Thunderbird, or SeaMonkey installation by looking for their executables or checking system package managers. On Windows, check Program Files for Mozilla Firefox, Mozilla Thunderbird, or SeaMonkey folders. On Linux, run 'rpm -qa | grep -i mozilla' or 'dpkg -l | grep -i mozilla'. On macOS, check /Applications for these applications.
    Affected if Any of these three products (Firefox, Thunderbird, SeaMonkey) is installed
  2. Determine Firefox version
    For Firefox: Open the application, go to Help > About Mozilla Firefox, or navigate to 'about: Firefox' in the address bar. Alternatively, check the version file in the installation directory or run 'firefox -v' from command line.
    Affected if Version is 2.0.0.14 or earlier, including all 2.0.x versions listed in the affected range
  3. Determine Thunderbird version
    For Thunderbird: Open the application, go to Help > About Mozilla Thunderbird, or navigate to 'about: Thunderbird' in the address bar. Alternatively, check the version file in the installation directory or run 'thunderbird -v' from command line.
    Affected if Version is 2.0.0.14 or earlier, including all 2.0.0.x versions listed in the affected range
  4. Determine SeaMonkey version
    For SeaMonkey: Open the application, go to Help > About SeaMonkey, or navigate to 'about: SeaMonkey' in the address bar. Alternatively, check the version file in the installation directory.
    Affected if Version is 1.1.9 or earlier, including all 1.1.x versions listed in the affected range
  5. Verify JavaScript is enabled
    Check if JavaScript is enabled in the affected application. In Firefox: go to Tools > Options > Content and verify 'Enable JavaScript' is checked. In Thunderbird: go to Edit > Preferences > Advanced > Scripts & Plugins and check if JavaScript is enabled. In SeaMonkey: go to Edit > Preferences > Advanced and check JavaScript settings.
    Affected if JavaScript is enabled (the vulnerability resides in the JavaScript engine, so this is required for exploitation)

You are affected if any of Firefox 2.0.0.14 or earlier, Thunderbird 2.0.0.14 or earlier, or SeaMonkey 1.1.9 or earlier is installed AND JavaScript is enabled in that application.

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
Upgrade available Upgrade to a release after 2.0.0.14
Interim mitigation

Upgrade to Firefox 2.0.0.15+, Thunderbird 2.0.0.14+, or SeaMonkey 1.1.10+ respectively, or disable JavaScript in these applications as a workaround.

Recommended fix High confidence

Firefox 2.0.0.15, SeaMonkey 1.1.10, Thunderbird 2.0.0.15

  1. Upgrade Firefox to version 2.0.0.15
  2. Upgrade SeaMonkey to version 1.1.10
  3. Upgrade Thunderbird to version 2.0.0.15
  4. After upgrading, verify the installation by checking Help > About in the application
Caveat These are very old legacy versions. Modern browsers and email clients have significantly changed. Ensure compatibility with any legacy systems or add-ons that may depend on these older versions.

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

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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