Unity Firefox ExtensionWeb browser · Ps Project Management Team

CVE-2012-0960

HIGH · 7.5 CVSS v2.0 Published 2012-11-24
Fix available
A fix is available. Upgrade to after 2.4.0 or later.
See remediation →
84/100
Remediation priority · High
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
Unity integration extension (unity-firefox-extension) before 2.4.1 for Firefox does not properly handle callbacks, which allows remote attackers to cause a denial of service (Firefox crash) and possibly execute arbitrary code via a crafted request.

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 Unity Firefox extension (unity-firefox-extension) before version 2.4.1 contains a callback handling flaw that can be exploited via crafted requests from remote websites. This improper handling can cause Firefox to crash (denial of service) and potentially allow arbitrary code execution.

MitigationUpgrade unity-firefox-extension to version 2.4.1 or later to patch the callback handling vulnerability. Users should avoid visiting untrusted websites until the patch is applied.

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
Unity Firefox ExtensionWeb browser
Affected:<= 2.4.0= 0.02= 0.2.1= 0.3= 0.3.1= 2.1= 2.2= 2.3= 2.3.1= 2.3.2= 2.3.3= 2.3.4

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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. Verify Unity Firefox extension is installed
    Open Firefox and navigate to Add-ons > Extensions, or enter 'about:addons' in the address bar. Look for 'Unity' or 'unity-firefox-extension' in the list of installed extensions.
    Affected if The Unity Firefox extension appears in the list of installed extensions.
  2. Determine the installed version number
    In the Firefox Add-ons Manager (about:addons), click on the Unity extension entry and view the version number displayed in the details panel. Alternatively, locate the extension folder in the Firefox profile directory (typically in ~/.mozilla/firefox/*/extensions/ or %AppData%/Mozilla/Firefox/Profiles/*/extensions/) and check the install.rdf or manifest.json file for the version attribute.
    Affected if The version number matches any of the following: 0.02, 0.2.1, 0.3, 0.3.1, 2.1, 2.2, 2.3, 2.3.1, 2.3.2, 2.3.3, 2.3.4, or any version 2.4.0 or lower.
  3. Confirm the extension is enabled
    In the Firefox Add-ons Manager, verify that the Unity extension shows a status of 'Enabled' rather than 'Disabled'.
    Affected if The extension is enabled and the version is in the affected list.
  4. Check if JavaScript is enabled for websites
    In Firefox, go to Settings > Privacy & Security > Permissions, or enter 'about:preferences#privacy' and verify the JavaScript permission settings. The vulnerability is triggered via crafted requests from remote websites.
    Affected if JavaScript is allowed to run on websites (default setting), which enables the attack vector for this vulnerability.

You are affected if the Unity Firefox extension is installed, enabled, and its version is 2.4.0 or lower, or matches any of the specific vulnerable version numbers listed.

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.

From vendor data
Upgrade available Upgrade to a release after 2.4.0
Interim mitigation

Upgrade unity-firefox-extension to version 2.4.1 or later to patch the callback handling vulnerability. Users should avoid visiting untrusted websites until the patch is applied.

Fix this in Unity Firefox Extension Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-0960 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-0960 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