CVE-2011-2984
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 · uneditedMozilla Firefox before 3.6.20, SeaMonkey 2.x, Thunderbird 3.x before 3.1.12, and possibly other products does not properly handle the dropping of a tab element, which allows remote attackers to execute arbitrary JavaScript code with chrome privileges by establishing a content area and registering for drop events.
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 confidenceA flaw in Mozilla Firefox before 3.6.20, SeaMonkey 2.x, and Thunderbird 3.x before 3.1.12 allows remote attackers to execute arbitrary JavaScript code with chrome (privileged) privileges by establishing a malicious content area and registering for drop events on tab elements. This is a privilege escalation vulnerability where web content can escape the sandbox.
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<= 3.6.19= 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= 2.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.7= 2.0.8= 2.0.9= 2.0.10= 2.0.11= 3.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 3.0.5= 3.0.6= 3.0.7= 3.0.8= 3.0.9= 3.0.10= 3.0.11CVSS 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 Firefox versionOpen Firefox and navigate to Help > About Mozilla Firefox, or enter 'about:Firefox' in the address bar. Alternatively, check the file properties of firefox.exe in the installation directory.Affected if The version displayed is 1.0.x, 1.5.x, or 3.6.19 or earlier
-
Check SeaMonkey versionOpen SeaMonkey and navigate to Help > About SeaMonkey. Alternatively, check the file properties of seamonkey.exe in the installation directory.Affected if The version displayed is 2.0 through 2.0.11 inclusive
-
Check Thunderbird versionOpen Thunderbird and navigate to Help > About Thunderbird. Alternatively, check the file properties of thunderbird.exe in the installation directory.Affected if The version displayed is 3.0 through 3.0.11 inclusive
-
Check Windows registry for installed Mozilla productsOpen Registry Editor and check HKLM\SOFTWARE\Mozilla\Mozilla Firefox\CurrentVersion (or HKLM\SOFTWARE\Mozilla\SeaMonkey\CurrentVersion, or HKLM\SOFTWARE\Mozilla\Thunderbird\CurrentVersion) for the installed version string.Affected if Any of these registry keys show a version that matches the affected ranges above
You are affected if any Mozilla Firefox 1.0.x, 1.5.x, or 3.6.19 and earlier; SeaMonkey 2.0 through 2.0.11; or Thunderbird 3.0 through 3.0.11 is installed on the system.
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 · scopedUpgrade to Firefox 3.6.20 or later, Thunderbird 3.1.12 or later, or SeaMonkey 2.x to the patched version. Organizations should remove deprecated Mozilla products from their environment.
Firefox 3.6.20+, SeaMonkey 2.0.4+, Thunderbird 3.1.12+ (or migrate to current supported versions)
- Upgrade Firefox to version 3.6.20 or later, or preferably to a supported modern version (Firefox ESR or current release)
- Upgrade SeaMonkey to version 2.0.4 or later if continuing to use SeaMonkey
- Upgrade Thunderbird to version 3.1.12 or later, or preferably to a supported modern version
- After upgrading, verify the version by checking 'Help > About' in the application menu
- Ensure automatic updates are enabled to receive future security patches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2011-2984 — 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-2984 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