FirefoxWeb browser · Mozilla
CVE-2011-2365
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 · uneditedUnspecified vulnerability in the browser engine in Mozilla Firefox 3.6.x before 3.6.18 and Thunderbird before 3.1.11 allows remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors, a different vulnerability than CVE-2011-2364.
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 confidenceMemory corruption vulnerability in the Mozilla Firefox and Thunderbird browser engine allows remote attackers to cause denial of service via application crash or potentially execute arbitrary code through unknown attack vectors.
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
= 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.6.11= 3.6.12= 3.6.13= 3.6.14<= 3.1.10= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.7= 0.7.1= 0.7.2= 0.7.3= 0.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Firefox versionOpen Firefox, go to Help > About Firefox, or navigate to about:support, or run 'firefox --version' from command lineAffected if Version matches 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.6.11, 3.6.12, 3.6.13, or 3.6.14
-
Check installed Thunderbird versionOpen Thunderbird, go to Help > About Thunderbird, or navigate to about:support, or run 'thunderbird --version' from command lineAffected if Version is 3.1.10 or lower, or matches 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
You are affected if either Firefox version 3.6.x (specifically 3.6.2-3.6.14) or Thunderbird version 3.1.10 or lower, or any 0.x version, is installed.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Mozilla Firefox to version 3.6.18 or higher and Thunderbird to version 3.1.11 or higher to patch the vulnerability. Prioritize patching given the critical CVSS 10 severity indicating potential for remote code execution.
Firefox 3.6.18 or Thunderbird 3.1.11
- 1. Back up all personal data (bookmarks, passwords, emails) from the current installation
- 2. Download Firefox 3.6.18 (or later 3.6.x release) from the Mozilla archives or a trusted mirror
- 3. Download Thunderbird 3.1.11 (or later 3.1.x release) from the Mozilla archives or a trusted mirror
- 4. Install the new version over the existing installation, or to a separate directory
- 5. Verify the installed version matches the fixed release (Firefox: 3.6.18+, Thunderbird: 3.1.11+)
- 6. Test critical functionality (browsing, email receiving/sending) to confirm the application operates without crashes
- 7. After verification, remove the older vulnerable version if installed to a separate directory
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-2365 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-2365 in production — separate from our analysis above.
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.
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.
- 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