CVE-2011-3647
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 · uneditedThe JSSubScriptLoader in Mozilla Firefox before 3.6.24 and Thunderbird before 3.1.6 does not properly handle XPCNativeWrappers during calls to the loadSubScript method in an add-on, which makes it easier for remote attackers to gain privileges via a crafted web site that leverages certain unwrapping behavior, a related issue to CVE-2011-3004.
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 confidenceThe JSSubScriptLoader in Firefox before 3.6.24 and Thunderbird before 3.1.6 fails to properly handle XPCNativeWrappers when the loadSubScript method is called by add-ons. This allows a malicious website to bypass security wrapper protections and execute code with elevated privileges, enabling remote code execution or privilege escalation attacks.
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.23= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.6.1= 0.7= 0.7.1= 0.8= 0.9<= 3.1.5= 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/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.
-
Identify installed Mozilla productCheck for Firefox or Thunderbird installation by examining program directories (e.g., C:\Program Files\Mozilla Firefox or C:\Program Files\Mozilla Thunderbird on Windows, /Applications/Firefox or /Applications/Thunderbird on macOS, /usr/lib/firefox or /usr/lib/thunderbird on Linux)Affected if Neither Firefox nor Thunderbird is installed on the system
-
Determine Firefox versionFor Firefox: open Help > About Firefox, or check version.json in the installation directory, or run 'firefox --version' from command lineAffected if Installed version is 3.6.23 or earlier, or falls within versions 0.1 through 0.9 (e.g., 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.6.1, 0.7, 0.7.1, 0.8, 0.9)
-
Determine Thunderbird versionFor Thunderbird: open Help > About Thunderbird, or check version.json in the installation directory, or run 'thunderbird --version' from command lineAffected if Installed version is 3.1.5 or earlier, or falls within versions 0.1 through 0.8 (e.g., 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)
-
Confirm add-on usage (optional context)Examine installed add-ons in the profiles folder (e.g., %APPDATA%\Mozilla\Firefox\Profiles\*.default\extensions on Windows) for extensions that may use the loadSubScript JavaScript methodAffected if Extensions using loadSubScript are present and the browser version falls within affected ranges - this indicates potential exploitability in a web browsing context
A system is affected if Firefox version 3.6.23 or earlier (including 0.x series up to 0.9) or Thunderbird version 3.1.5 or earlier (including 0.x series up to 0.8) is installed and the user runs untrusted websites or has add-ons that leverage the loadSubScript method.
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 affected systems to Firefox 3.6.24 or later, or Thunderbird 3.1.6 or later. For legacy systems that cannot upgrade, consider replacing with supported browser versions or implementing network-level blocking of untrusted websites.
Firefox 3.6.24 or later; Thunderbird 3.1.6 or later
- 1. Verify current Firefox version by navigating to Help > About Mozilla Firefox
- 2. Verify current Thunderbird version by navigating to Help > About Mozilla Thunderbird
- 3. For Firefox: Download and install Firefox 3.6.24 or later from the official Mozilla website (https://www.mozilla.org/firefox/)
- 4. For Thunderbird: Download and install Thunderbird 3.1.6 or later from the official Mozilla website (https://www.thunderbird.net/)
- 5. After installation, restart the application
- 6. Verify the update was successful by checking the version number again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-3647 — 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-3647 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