dbcve.org
FirefoxWeb browser · Mozilla

CVE-2011-0065

HIGH · 10.0 CVSS v2.0 Published 2011-05-07
Fix available
A fix is available. Upgrade to after 2.0.13 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
Use-after-free vulnerability in Mozilla Firefox before 3.5.19 and 3.6.x before 3.6.17, and SeaMonkey before 2.0.14, allows remote attackers to execute arbitrary code via vectors related to OBJECT's mChannel.

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

Use-after-free vulnerability in the mChannel property of the OBJECT element in Mozilla Firefox before 3.5.19 and 3.6.x before 3.6.17, and SeaMonkey before 2.0.14, allows remote attackers to execute arbitrary code via specially crafted web pages.

MitigationUpgrade affected installations to Firefox 3.5.19+, 3.6.17+, or SeaMonkey 2.0.14+ to eliminate the 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.6.9= 3.6.10= 3.6.11= 3.6.12= 3.6.13
SeamonkeyApplication
Affected:<= 2.0.13= 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

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. Identify the installed Mozilla product
    Open the application and check Help > About (Firefox or SeaMonkey) to confirm which product is installed
    Affected if The product is Firefox or SeaMonkey
  2. Check Firefox version
    In Firefox, enter 'about:support' in the address bar or go to Help > About Firefox to display the version number
    Affected if Firefox version is 3.6.x (any point release) or lower than 3.5.19
  3. Check SeaMonkey version
    In SeaMonkey, go to Help > About SeaMonkey to display the version number
    Affected if SeaMonkey version is 2.0.13 or lower, or any 1.x version up to 1.1
  4. Compare against affected Firefox ranges
    Firefox is affected if version is 3.6.x (including 3.6, 3.6.2-3.6.13) or below 3.5.19
    Affected if Installed Firefox version matches one of the listed affected versions (3.6, 3.6.2, 3.6.3, 3.6.4, 3.6.6-3.6.13) or is below 3.5.19
  5. Compare against affected SeaMonkey ranges
    SeaMonkey is affected if version is 2.0.13 or lower, or any 1.x version (1.0-1.1)
    Affected if Installed SeaMonkey version is 2.0.13 or lower, or falls within the 1.0.x to 1.1 range

A user is affected if they are running Firefox 3.6.x (any point release) or below 3.5.19, or SeaMonkey 2.0.13 or lower or any 1.x version through 1.1.

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

Upgrade affected installations to Firefox 3.5.19+, 3.6.17+, or SeaMonkey 2.0.14+ to eliminate the vulnerability.

Recommended fix High confidence

Firefox 3.6.17 or later / SeaMonkey 2.0.14 or later

  1. 1. Back up any important bookmarks, passwords, and browser data before upgrading.
  2. 2. Download Firefox 3.6.17 or later (preferably the latest stable release such as Firefox ESR or current stable).
  3. 3. If using SeaMonkey, download SeaMonkey 2.0.14 or later.
  4. 4. Close all instances of the affected browser.
  5. 5. Install the updated browser version.
  6. 6. Verify the installed version matches or exceeds the fixed release (Firefox >= 3.6.17 or SeaMonkey >= 2.0.14).
Caveat Upgrading from Firefox 3.6.x to modern releases may have significant compatibility impacts with legacy plugins and add-ons; consider using Firefox ESR for smoother migration

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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