dbcve.org
FirefoxWeb browser · Mozilla

CVE-2011-2375

HIGH · 10.0 CVSS v2.0 Published 2011-06-30
Fix available
A fix is available. Upgrade to after 4.0.1 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
Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 5.0 and Thunderbird through 3.1.11 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors.

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 · moderate confidence

Multiple unspecified vulnerabilities in the Mozilla browser engine allow remote attackers to cause memory corruption leading to denial of service (application crash) or potentially execute arbitrary code via unknown attack vectors.

MitigationUpgrade to Firefox 5.0 or later and Thunderbird 3.1.12 or later to obtain patched versions of the browser engine.

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:<= 4.0.1= 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.5= 1.5.0.1
ThunderbirdApplication
Affected:<= 3.1.11= 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
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 checks

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

  1. Check installed Firefox version
    Open Firefox, click Help > About Firefox. Alternatively, run 'firefox --version' from command line, or locate the executable and check its properties.
    Affected if Version is 4.0.1 or lower, or matches 1.0 through 1.0.8, 1.5, or 1.5.0.1
  2. Check installed Thunderbird version
    Open Thunderbird, click Help > About Thunderbird. Alternatively, run 'thunderbird --version' from command line, or locate the executable and check its properties.
    Affected if Version is 3.1.11 or lower, or matches 0.1 through 0.7.3, or version 0.8
  3. Confirm product and version against affected list
    Compare your detected version number to the affected versions listed for the respective product.
    Affected if Your installed version appears in the affected version ranges

You are affected if Firefox 4.0.1 or lower (or specific 1.x versions) or Thunderbird 3.1.11 or lower (or specific 0.x versions) is installed.

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

Upgrade to Firefox 5.0 or later and Thunderbird 3.1.12 or later to obtain patched versions of the browser engine.

Recommended fix High confidence

Firefox 5.0+ and Thunderbird 5.0+

  1. 1. Check current Firefox version by navigating to Help > About Firefox
  2. 2. Check current Thunderbird version by navigating to Help > About Thunderbird
  3. 3. Download Firefox 5.0 or later from the official Mozilla website (www.mozilla.org)
  4. 4. Download Thunderbird 5.0 or later from the official Mozilla website (www.mozilla.org)
  5. 5. Close all instances of the affected application
  6. 6. Run the installer for the new version
  7. 7. Restart the application after installation completes
  8. 8. Verify the version by checking Help > About to confirm the installed version
Caveat Major version upgrades may introduce changes to user interface, extensions compatibility, or bookmark/password migration; test extensions in a non-production environment before deploying organization-wide

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-2011-2375 — 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-2011-2375 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