dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-2767

HIGH · 9.3 CVSS v2.0 Published 2010-09-09
Fix available
A fix is available. Upgrade to after 3.5.11 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
The navigator.plugins implementation in Mozilla Firefox before 3.5.12 and 3.6.x before 3.6.9, Thunderbird before 3.0.7 and 3.1.x before 3.1.3, and SeaMonkey before 2.0.7 does not properly handle destruction of the DOM plugin array, which might allow remote attackers to cause a denial of service (application crash) or execute arbitrary code via crafted access to the navigator object, related to a "dangling pointer vulnerability."

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

A dangling pointer vulnerability in the navigator.plugins implementation in Mozilla Firefox, Thunderbird, and SeaMonkey allows remote attackers to cause denial of service or execute arbitrary code via crafted access to the navigator object during destruction of the DOM plugin array.

MitigationUpgrade affected Mozilla products to patched versions (Firefox 3.5.12+/3.6.9+, Thunderbird 3.0.7+/3.1.3+, SeaMonkey 2.0.7+) 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
FirefoxWeb browser
Affected:= 3.6= 3.6.2= 3.6.3= 3.6.4= 3.6.6= 3.6.7= 3.6.8<= 3.5.11= 1.0= 1.0.1= 1.0.2= 1.0.3
SeamonkeyApplication
Affected:<= 2.0.6= 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
ThunderbirdApplication
Affected:<= 3.0.6= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.7= 0.7.1= 0.7.2= 0.7.3= 0.8

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. Identify installed Mozilla product and version
    Check version via Help > About (Firefox/Thunderbird/SeaMonkey), or via command line: 'firefox --version', 'thunderbird --version', 'seamonkey --version' on Linux; or check registry on Windows (HKLM\Software\Mozilla\Mozilla Firefox\CurrentVersion)
    Affected if The product is Firefox <= 3.5.11 or 3.6.x (excluding 3.6.9+); Thunderbird <= 3.0.6 (excluding 3.0.7+/3.1.3+); or SeaMonkey <= 2.0.6 (excluding 2.0.7+) or SeaMonkey 1.0-1.1 series
  2. Confirm JavaScript is enabled in the browser
    In Firefox: go to Options > Content (or Preferences > Content on older versions), verify 'Enable JavaScript' is checked. In Thunderbird: Edit > Preferences > Privacy & Security > Scripts & Plugins. In SeaMonkey: Edit > Preferences > Advanced > Scripts & Plugins.
    Affected if JavaScript is enabled (required for the navigator.plugins manipulation to occur)
  3. Check for presence of browser plugins
    Access navigator.plugins via JavaScript console: type 'navigator.plugins' in the error console or developer tools. This exposes the DOM plugin array.
    Affected if The browser has plugins installed and navigator.plugins is accessible (the vulnerability triggers during destruction of this array)

The environment is affected if a vulnerable Firefox (3.5.x or 3.6.x), Thunderbird (3.0.x or earlier), or SeaMonkey (1.x or 2.0.6 and below) is in use with JavaScript enabled and the user accesses content that triggers navigator.plugins manipulation.

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 3.5.11
Interim mitigation

Upgrade affected Mozilla products to patched versions (Firefox 3.5.12+/3.6.9+, Thunderbird 3.0.7+/3.1.3+, SeaMonkey 2.0.7+) to remediate this vulnerability.

Recommended fix High confidence

Firefox 3.6.9 (or Firefox 3.5.12+); Thunderbird 3.0.7 (or Thunderbird 3.1.3+); SeaMonkey 2.0.7

  1. Check the current installed version of Firefox, Thunderbird, or SeaMonkey by accessing the Help > About menu in the application
  2. Download the appropriate fixed version: Firefox 3.6.9 or later (or migrate to Firefox 3.5.12+), Thunderbird 3.0.7 or later (or migrate to Thunderbird 3.1.3+), or SeaMonkey 2.0.7 or later
  3. Close all instances of the affected application
  4. Run the installer for the fixed version
  5. Restart the application after installation completes
  6. Verify the installation by checking Help > About to confirm the version number matches the fixed release
Caveat Upgrading to newer major releases may introduce changes to extensions, themes, or bookmarks; consider testing in a non-production environment first

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-2767 — 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-2010-2767 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