dbcve.org
FirefoxWeb browser · Mozilla

CVE-2012-1967

HIGH · 10.0 CVSS v2.0 Published 2012-07-18
Fix available
A fix is available. Upgrade to after 2.10 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
Mozilla Firefox 4.x through 13.0, Firefox ESR 10.x before 10.0.6, Thunderbird 5.0 through 13.0, Thunderbird ESR 10.x before 10.0.6, and SeaMonkey before 2.11 do not properly implement the JavaScript sandbox utility, which allows remote attackers to execute arbitrary JavaScript code with improper privileges via a javascript: URL.

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

The JavaScript sandbox utility in Mozilla Firefox, Thunderbird, and SeaMonkey was improperly implemented, allowing javascript: URLs to execute arbitrary JavaScript code with elevated privileges. This represents a sandbox escape vulnerability where the intended security isolation of the JavaScript sandbox was bypassed.

MitigationUpdate affected Mozilla products to patched versions: Firefox 13.0.1+, Firefox ESR 10.0.6+, Thunderbird 13.0.1+, Thunderbird ESR 10.0.6+, or SeaMonkey 2.11+. Deploy via enterprise patch management where applicable.

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:= 4.0= 4.0.1= 5.0= 5.0.1= 6.0= 6.0.1= 6.0.2= 7.0= 7.0.1= 8.0= 8.0.1= 9.0
ThunderbirdApplication
Affected:= 5.0= 6.0= 6.0.1= 6.0.2= 7.0= 7.0.1= 8.0= 9.0= 9.0.1= 10.0= 10.0.1= 10.0.2
Thunderbird EsrApplication
Affected:= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.0.4= 10.0.5
SeamonkeyApplication
Affected:<= 2.10= 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 installed Mozilla product
    Check if Firefox, Thunderbird, or SeaMonkey is installed by looking for the executable in typical installation paths or checking installed programs. On Windows, check Program Files folder or registry. On Linux, check /usr/bin/ for firefox, thunderbird, or seamonkey. On macOS, check /Applications/.
    Affected if Any of the affected products (Firefox, Thunderbird, SeaMonkey) are installed
  2. Determine installed version number
    For Firefox: run 'firefox --version' or go to Help > About Firefox. For Thunderbird: run 'thunderbird --version' or go to Help > About Thunderbird. For SeaMonkey: go to Help > About SeaMonkey. Record the exact version number displayed.
    Affected if The version matches one listed in the affected versions for that product
  3. Compare against affected version list
    Match your installed version against the affected ranges: Firefox 4.0 through 9.0 (specific point releases listed), Thunderbird 5.0 through 10.0.2, Thunderbird ESR 10.0 through 10.0.5, SeaMonkey 1.0 through 2.10, or SeaMonkey 2.10 and below.
    Affected if The installed version is in the list of affected versions for that product
  4. Verify javascript: URL handling is possible
    The vulnerability is triggered when javascript: URLs are processed in certain contexts within the application. This is a built-in feature of the affected products used for bookmarklets and certain web functionality. No special configuration change is needed for the vulnerability to exist.
    Affected if The product is one of the affected versions and supports javascript: URL handling (default behavior in all affected versions)

A user is affected if they have any of the listed vulnerable versions of Firefox, Thunderbird, or SeaMonkey installed, as the sandbox escape vulnerability exists in the javascript: URL handling of those specific versions.

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.10
Interim mitigation

Update affected Mozilla products to patched versions: Firefox 13.0.1+, Firefox ESR 10.0.6+, Thunderbird 13.0.1+, Thunderbird ESR 10.0.6+, or SeaMonkey 2.11+. Deploy via enterprise patch management where applicable.

Recommended fix High confidence

Firefox 14.0+ or Firefox ESR 10.0.6+; Thunderbird 14.0+ or Thunderbird ESR 10.0.6+; SeaMonkey 2.11+

  1. Upgrade Firefox to version 14.0 or later (or Firefox ESR 10.0.6 or later if using the ESR branch)
  2. Upgrade Thunderbird to version 14.0 or later (or Thunderbird ESR 10.0.6 or later if using the ESR branch)
  3. Upgrade SeaMonkey to version 2.11 or later
Caveat These are legacy products from 2012; upgrading may require migration to newer product versions as these older branches are no longer supported

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-2012-1967 — 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-2012-1967 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