dbcve.org
FirefoxWeb browser · Mozilla

CVE-2011-0057

HIGH · 10.0 CVSS v2.0 Published 2011-03-02
Fix available
A fix is available. Upgrade to after 2.0.11 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
Use-after-free vulnerability in the Web Workers implementation in Mozilla Firefox before 3.5.17 and 3.6.x before 3.6.14, and SeaMonkey before 2.0.12, allows remote attackers to execute arbitrary code via vectors related to a JavaScript Worker and garbage collection.

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 Mozilla Firefox and SeaMonkey's Web Workers implementation allows remote attackers to execute arbitrary code by exploiting garbage collection timing with JavaScript Worker objects.

MitigationUpgrade to Firefox 3.5.17+, 3.6.14+, or SeaMonkey 2.0.12+ to patch 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.11= 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 browser and version
    For Firefox: access Help > About Firefox or navigate to about:support in the address bar. For SeaMonkey: access Help > About SeaMonkey. Note the exact version number displayed.
    Affected if Version matches Firefox 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, or 3.6.13; or SeaMonkey versions 1.0 through 1.1, or SeaMonkey 2.0.11 or earlier
  2. Confirm JavaScript is enabled
    Navigate to Firefox Options > Content (or SeaMonkey Edit > Preferences > Scripts & Plugins). Verify the Enable JavaScript checkbox is selected.
    Affected if JavaScript is enabled (the vulnerability requires JavaScript execution to trigger the Web Workers flaw)
  3. Determine if Web Workers are in use
    Review application source code for JavaScript Worker constructor calls (new Worker(), SharedWorker), or inspect loaded scripts for worker creation patterns.
    Affected if The application uses Web Workers (the vulnerability is triggered through JavaScript Worker objects)

Environment is affected if the installed Firefox or SeaMonkey version falls within the vulnerable range AND JavaScript with Web Workers functionality is enabled and actively used.

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

Upgrade to Firefox 3.5.17+, 3.6.14+, or SeaMonkey 2.0.12+ to patch the vulnerability.

Recommended fix High confidence

Firefox 3.6.14+ or Firefox 4.0+; SeaMonkey 2.0.12+

  1. 1. Back up all critical data and browser profiles before making changes
  2. 2. For Firefox 3.6.x users: Download and install Firefox 3.6.14 or later from mozilla.org
  3. 3. For SeaMonkey 2.x users: Download and install SeaMonkey 2.0.12 or later from mozilla.org
  4. 4. After installation, verify the version by navigating to Help > About in the application menu
  5. 5. Consider upgrading to a more recent Firefox release (4.0+) as Firefox 3.6.x is end-of-life
Caveat Firefox 3.6.x is end-of-life and no longer receives security updates; upgrading to modern Firefox may require adjusting to new interface and deprecated add-ons

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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