dbcve.org
FirefoxWeb browser · Mozilla

CVE-2011-3652

HIGH · 10.0 CVSS v2.0 Published 2011-11-09
Fix available
A fix is available. Upgrade to after 7.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
The browser engine in Mozilla Firefox before 8.0 and Thunderbird before 8.0 does not properly allocate memory, which allows remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unspecified 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

Memory allocation vulnerability in the Mozilla browser engine allows remote attackers to cause memory corruption leading to denial of service or potentially execute arbitrary code via unspecified vectors.

MitigationUpdate affected systems to Firefox 8.0 or later, and Thunderbird 8.0 or later to remediate the memory allocation flaw in 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:<= 7.0.1= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.6.1= 0.7= 0.7.1= 0.8= 0.9
ThunderbirdApplication
Affected:<= 7.0.1= 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
    Run 'firefox --version' or look in Help > About Firefox to find the exact version number
    Affected if The version is 7.0.1 or earlier, or matches any of these: 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.6.1, 0.7, 0.7.1, 0.8, 0.9, or any version <= 7.0.1
  2. Check installed Thunderbird version
    Run 'thunderbird --version' or look in Help > About Thunderbird to find the exact version number
    Affected if The version is 7.0.1 or earlier, or matches any of these: 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, or any version <= 7.0.1
  3. Verify no other Mozilla products are affected
    Check for other installed Mozilla applications that use the same browser engine (such as SeaMonkey) and note their versions
    Affected if Any Mozilla product using the same engine version as Firefox 7.0.1 or earlier is installed

You are affected if Firefox or Thunderbird version is 7.0.1 or any of the specific older versions listed (0.1 through 0.9 for Firefox, 0.1 through 0.8 for Thunderbird).

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

Update affected systems to Firefox 8.0 or later, and Thunderbird 8.0 or later to remediate the memory allocation flaw in the browser engine.

Recommended fix High confidence

Firefox 8.0+ and Thunderbird 8.0+

  1. 1. Back up any important data, including bookmarks, passwords, and extensions
  2. 2. Visit the official Mozilla Firefox download page (mozilla.org/firefox) or Thunderbird download page (mozilla.org/thunderbird)
  3. 3. Download version 8.0 or later for your operating system
  4. 4. Close all browser/email client instances completely
  5. 5. Run the installer and follow the prompts to install the new version
  6. 6. After installation, verify the version by navigating to Help > About Firefox or Help > About Thunderbird
  7. 7. Re-install any required extensions or add-ons that are compatible with version 8.0+
Caveat Firefox 8.0 introduced significant add-on compatibility changes; many older extensions may not work and will need to be updated or replaced

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

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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