FirefoxWeb browser · Mozilla

CVE-2010-0177

HIGH · 9.3 CVSS v2.0 Published 2010-04-05

Fix available

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

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Mozilla Firefox before 3.0.19, 3.5.x before 3.5.9, and 3.6.x before 3.6.2, and SeaMonkey before 2.0.4, frees the contents of the window.navigator.plugins array while a reference to an array element is still active, which allows remote attackers to execute arbitrary code or cause a denial of service (application crash) via unspecified vectors, related to a "dangling pointer vulnerability."

Technical summary

dbcve analysis · high confidence

Mozilla Firefox and SeaMonkey contain a dangling pointer vulnerability where the window.navigator.plugins array is freed while a reference to an array element remains active. This use-after-free condition allows remote attackers to execute arbitrary code or cause a denial of service via unspecified vectors.

MitigationUpdate affected Firefox versions (3.0.x before 3.0.19, 3.5.x before 3.5.9, 3.6.x before 3.6.2) and SeaMonkey before 2.0.4 to their latest patched versions 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

NVD · CPE data

FirefoxWeb browser

Affected:= 3.6<= 3.0.17= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.6.1= 0.7= 0.7.1= 0.8

SeamonkeyApplication

Affected:<= 2.0.3= 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 Firefox browser version

Open Firefox, go to Help > About Mozilla Firefox, or run 'firefox --version' from command line

Affected if Version matches 3.6, or is 3.0.x at 3.0.17 or earlier, or is 0.x series (0.1 through 0.8)
Identify SeaMonkey browser version

Open SeaMonkey, go to Help > About SeaMonkey, or run 'seamonkey --version' from command line

Affected if Version is 2.0.3 or earlier, or is in the 1.0.x series (1.0 through 1.1)
Confirm JavaScript is enabled

In browser, go to Options/Preferences > Content and verify 'Enable JavaScript' is checked, or inspect navigator.javaEnabled() returns true

Affected if JavaScript is enabled - the vulnerability is triggered through JavaScript access to window.navigator.plugins array

User is affected if they run a Firefox or SeaMonkey version matching the affected list AND have JavaScript enabled in their browser settings.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 3.0.17

Interim mitigation

Update affected Firefox versions (3.0.x before 3.0.19, 3.5.x before 3.5.9, 3.6.x before 3.6.2) and SeaMonkey before 2.0.4 to their latest patched versions to remediate this vulnerability.

Recommended fix High confidence

Firefox 3.6.2 (or 3.0.19/3.5.9 depending on branch); SeaMonkey 2.0.4

1. Identify the currently installed Firefox or SeaMonkey version from the Help > About menu
2. For Firefox users: If running 3.6.x, upgrade to Firefox 3.6.2 or later; if running 3.0.x, upgrade to Firefox 3.0.19 or later; if running 3.5.x, upgrade to Firefox 3.5.9 or later
3. For SeaMonkey users: If running 2.0.x or earlier, upgrade to SeaMonkey 2.0.4 or later
4. Download the appropriate fixed version from the official Mozilla archives or use the automatic update feature (Help > Check for Updates)
5. Restart the browser after installation
6. Verify the version has been updated by checking Help > About

Caveat These are very old browser versions from 2010; upgrading to modern Firefox (current ESR or stable) may break compatibility with legacy add-ons and older websites

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

Fix this in Firefox Scoped from the published advisory

Consultation1.0 h
Implementation1.0 h
Testing1.0 h
Review / QA1.0 h

4.0 hours of engineering $750

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,200.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2010-0177 — 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-0177 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2010-0177?

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 3.0.17 or later

Severity 9.3 High

Exploit likelihood EPSS, next 30 days 7.0%

Affects: Firefox

Remediation

A high-priority fix

Fix this in Firefox 4 hrs · Low

Typical engagement from $750

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2010-0177 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