dbcve.org
FirefoxWeb browser · Mozilla

CVE-2010-3183

HIGH · 9.3 CVSS v2.0 Published 2010-10-21
Fix available
A fix is available. Upgrade to after 3.5.13 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 LookupGetterOrSetter function in js3250.dll in Mozilla Firefox before 3.5.14 and 3.6.x before 3.6.11, Thunderbird before 3.0.9 and 3.1.x before 3.1.5, and SeaMonkey before 2.0.9 does not properly support window.__lookupGetter__ function calls that lack arguments, which allows remote attackers to execute arbitrary code or cause a denial of service (incorrect pointer dereference and application crash) via vectors involving a "dangling pointer" and the JS_ValueToId function.

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

Memory corruption vulnerability in the JavaScript engine (js3250.dll) of Mozilla Firefox, Thunderbird, and SeaMonkey. The LookupGetterOrSetter function improperly handles window.__lookupGetter__ calls without arguments, leading to a dangling pointer that can be dereferenced incorrectly via JS_ValueToId, potentially allowing arbitrary code execution or causing a denial of service via application crash.

MitigationUpgrade to Mozilla Firefox 3.5.14+/3.6.11+, Thunderbird 3.0.9+/3.1.5+, or SeaMonkey 2.0.9+ which contain the patched js3250.dll with proper argument validation in LookupGetterOrSetter.

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.6.9= 3.6.10<= 3.5.13= 1.0= 1.0.1
SeamonkeyApplication
Affected:<= 2.0.8= 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.8= 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 the application version: For Firefox, go to Help > About Firefox. For Thunderbird, go to Help > About Thunderbird. For SeaMonkey, go to Help > About SeaMonkey. Record the exact version number displayed.
    Affected if The product is Firefox, Thunderbird, or SeaMonkey and the version matches any of the affected versions listed in the CVE
  2. Verify product is in the affected family
    Confirm the installed application is one of: Mozilla Firefox, Mozilla Thunderbird, or Mozilla SeaMonkey. This CVE does not affect other browsers or products.
    Affected if The installed product is not Firefox, Thunderbird, or SeaMonkey
  3. Compare Firefox version against affected ranges
    If Firefox is installed, check if the version is 3.6 (any of 3.6, 3.6.2, 3.6.3, 3.6.4, 3.6.6, 3.6.7, 3.6.8, 3.6.9, 3.6.10), or 3.5.x up to and including 3.5.13, or 1.0.x (1.0, 1.0.1).
    Affected if Firefox version is exactly 3.6, 3.6.2, 3.6.3, 3.6.4, 3.6.6, 3.6.7, 3.6.8, 3.6.9, 3.6.10, or between 1.0 and 3.5.13 inclusive, or 1.0.1
  4. Compare SeaMonkey version against affected ranges
    If SeaMonkey is installed, check if the version is 2.0.8 or lower, or any 1.0.x version (1.0 through 1.1).
    Affected if SeaMonkey version is 2.0.8 or lower, or is 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, or 1.1
  5. Compare Thunderbird version against affected ranges
    If Thunderbird is installed, check if the version is 3.0.8 or lower, or any 0.x version (0.1 through 0.8).
    Affected if Thunderbird version is 3.0.8 or lower, or is 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.7, 0.7.1, 0.7.2, 0.7.3, or 0.8

The environment is affected if either Firefox, Thunderbird, or SeaMonkey is installed and the version exactly matches one of the versions listed in the CVE affected products, since the vulnerability exists in the js3250.dll JavaScript engine component used by all three products.

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.13
Interim mitigation

Upgrade to Mozilla Firefox 3.5.14+/3.6.11+, Thunderbird 3.0.9+/3.1.5+, or SeaMonkey 2.0.9+ which contain the patched js3250.dll with proper argument validation in LookupGetterOrSetter.

Recommended fix High confidence

Firefox 3.6.11 or later / Firefox ESR; Thunderbird 3.0.9+ or 3.1.5+; SeaMonkey 2.0.9+

  1. Identify which Mozilla product (Firefox, Thunderbird, or SeaMonkey) is installed and note the current version
  2. For Firefox 3.6.x users: Upgrade to Firefox 3.6.11 or later (or migrate to a supported Firefox ESR/release)
  3. For Thunderbird users: If on 3.0.x, upgrade to Thunderbird 3.0.9 or later; if on 3.1.x, upgrade to Thunderbird 3.1.5 or later
  4. For SeaMonkey users: Upgrade to SeaMonkey 2.0.9 or later
  5. After upgrading, verify the installed version matches or exceeds the fixed release
Caveat These are legacy versions from 2010; upgrading may introduce compatibility issues with older plugins or extensions designed for the 3.x product line

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,030
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,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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