FirefoxWeb browser · Mozilla

CVE-2010-1198

HIGH · 9.3 CVSS v2.0 Published 2010-06-24

Fix available

A fix is available. Upgrade to after 2.0.4 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Use-after-free vulnerability in Mozilla Firefox 3.5.x before 3.5.10 and 3.6.x before 3.6.4, and SeaMonkey before 2.0.5, allows remote attackers to execute arbitrary code via vectors involving multiple plugin instances.

Technical summary

dbcve analysis · high confidence

Use-after-free vulnerability in the browser plugin handling code allows remote attackers to execute arbitrary code via vectors involving multiple plugin instances. The flaw exists in Firefox 3.5.x before 3.5.10, Firefox 3.6.x before 3.6.4, and SeaMonkey before 2.0.5.

MitigationUpdate affected browsers to Firefox 3.5.10+, 3.6.4+, or SeaMonkey 2.0.5+ to patch the use-after-free vulnerability. Organizations should deploy browser updates through standard patch management.

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

Affected products & versions

NVD · CPE data

FirefoxWeb browser

Affected:= 3.5= 3.5.1= 3.5.2= 3.5.3= 3.5.4= 3.5.5= 3.5.6= 3.5.7= 3.5.9= 3.6= 3.6.2= 3.6.3

SeamonkeyApplication

Affected:<= 2.0.4= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8= 1.0.9= 1.1

CVSS breakdown

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?

dbcve checks

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

Identify the installed browser product

Open the application and navigate to Help > About (Firefox or SeaMonkey) to determine which browser is installed

Affected if The product is Mozilla Firefox or SeaMonkey
Determine the Firefox version

In Firefox, go to Help > About Firefox. Note the full version number displayed (for example, 3.5.9 or 3.6.3)

Affected if The version is 3.5.x before 3.5.10, or 3.6.x before 3.6.4 (versions 3.5.0 through 3.5.9, and 3.6.0 through 3.6.3)
Determine the SeaMonkey version

In SeaMonkey, go to Help > About SeaMonkey. Note the full version number displayed

Affected if The version is 2.0.4 or lower, or any 1.x version (1.0 through 1.1)
Verify multiple plugins could be present

Check if the browser has multiple plugins enabled: in Firefox, navigate to about:plugins. Look for more than one plugin instance loaded (common plugins include Adobe Flash, Java, Silverlight)

Affected if Multiple browser plugins are installed and enabled, which is the condition required to trigger the use-after-free flaw

A defender is affected if they are running Firefox versions 3.5.0-3.5.9 or 3.6.0-3.6.3, or SeaMonkey versions 2.0.4 or lower or any 1.x version, AND have multiple browser plugins enabled simultaneously.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 2.0.4

Interim mitigation

Update affected browsers to Firefox 3.5.10+, 3.6.4+, or SeaMonkey 2.0.5+ to patch the use-after-free vulnerability. Organizations should deploy browser updates through standard patch management.

Recommended fix High confidence

Firefox 3.5.10+/3.6.4+ or SeaMonkey 2.0.5+

Upgrade Firefox 3.5.x to version 3.5.10 or later
Upgrade Firefox 3.6.x to version 3.6.4 or later
Upgrade SeaMonkey to version 2.0.5 or later

Caveat These are very old browser versions (2010); upgrading to modern browser versions may break compatibility with legacy web applications or older operating systems

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

Fix this in Firefox Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing2.0 h
Review / QA1.0 h

9.0 hours of engineering $1,600

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-1198 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2010-1198?

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.

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

At a glance

A fix existsUpgrade to after 2.0.4 or later

Severity 9.3 High

Exploit likelihood EPSS, next 30 days 4.8%

Affects: Firefox

Remediation

A high-priority fix

Fix this in Firefox 9 hrs · Low

Typical engagement from $1,600

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2010-1198 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References