CVE-2008-2798
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 · uneditedMultiple 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 layout 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 · high confidenceMultiple critical vulnerabilities in the Mozilla layout engine affecting Firefox before 2.0.0.15, Thunderbird before 2.0.0.14, and SeaMonkey before 1.1.10 allow remote attackers to potentially execute arbitrary code or cause application crashes via unspecified vectors.
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<= 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<= 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<= 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.12CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Mozilla productCheck for presence of Firefox, Thunderbird, or SeaMonkey in your system. On Windows, look in Program Files for Mozilla Firefox, Mozilla Thunderbird, or SeaMonkey folders. On Linux, check /usr/bin for firefox, thunderbird, or seamonkey commands. On macOS, check /Applications for these applications.Affected if Any of Firefox, Thunderbird, or SeaMonkey is installed
-
Determine Firefox versionFor Firefox: Open browser, go to Help > About Firefox, or enter 'about:Firefox' in the address bar, or run 'firefox --version' from command line.Affected if Version is 2.0, or 2.0.0.1 through 2.0.0.14, or any version <= 2.0.0.14
-
Determine Thunderbird versionFor Thunderbird: Open application, go to Help > About Thunderbird, or run 'thunderbird --version' from command line.Affected if Version is 2.0.0.0 through 2.0.0.14, or any version <= 2.0.0.14 (excluding 2.0.0.13 and 2.0.0.14 based on the list)
-
Determine SeaMonkey versionFor SeaMonkey: Open application, go to Help > About SeaMonkey, or run 'seamonkey --version' from command line.Affected if Version is 1.1, 1.1.2 through 1.1.9, or any version <= 1.1.9
If any of these Mozilla products are installed and the detected version matches the affected ranges listed (Firefox <= 2.0.0.14, Thunderbird <= 2.0.0.14, SeaMonkey <= 1.1.9), the environment is vulnerable to CVE-2008-2798.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate affected Mozilla products to the patched versions (Firefox 2.0.0.15+, Thunderbird 2.0.0.14+, SeaMonkey 1.1.10+) or migrate to current supported versions of these applications.
Firefox 2.0.0.15+ | Thunderbird 2.0.0.15+ | SeaMonkey 1.1.10+
- Identify the installed Mozilla product (Firefox, Thunderbird, or SeaMonkey) and current version
- Backup any necessary data and bookmarks
- Uninstall the current vulnerable version
- Download the fixed version: Firefox 2.0.0.15 or later, Thunderbird 2.0.0.15 or later, or SeaMonkey 1.1.10 or later
- Install the fixed version
- Restart the application and verify it runs without errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2008-2798 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- secunia.com
- lists.opensuse.org
- rhn.redhat.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- security.gentoo.org
- slackware.com
- slackware.com
- slackware.com
- wiki.rpath.com
- www.debian.org
- www.debian.org
- www.debian.org
- www.debian.org
- www.mandriva.com
- www.mandriva.com
- www.mozilla.org
- www.mozilla.org
- www.redhat.com
- www.redhat.com
- www.redhat.com
- www.securityfocus.com
- www.securityfocus.com
- www.securitytracker.com
- www.ubuntu.com
- www.ubuntu.com
- www.vupen.com
- bugzilla.mozilla.org
- bugzilla.mozilla.org
- bugzilla.mozilla.org
- issues.rpath.com
- oval.cisecurity.org
- www.redhat.com
- www.redhat.com
- www.redhat.com
- www.redhat.com
- www.redhat.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2008-2798 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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