dbcve.org
FirefoxWeb browser · Mozilla

CVE-2011-0058

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
Buffer overflow in Mozilla Firefox before 3.5.17 and 3.6.x before 3.6.14, and SeaMonkey before 2.0.12, on Windows allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a long string that triggers construction of a long text run.

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

A buffer overflow vulnerability in Mozilla Firefox (versions before 3.5.17 and 3.6.x before 3.6.14) and SeaMonkey (before 2.0.12) on Windows allows remote attackers to execute arbitrary code or cause memory corruption by tricking users into visiting a webpage containing a long string that triggers construction of a long text run.

MitigationUpgrade affected browsers to Firefox 3.5.17+, 3.6.14+, or SeaMonkey 2.0.12+ respectively. For enterprise environments, deploy the updated versions via patch management systems and verify compliance.

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 product
    Check if Mozilla Firefox or SeaMonkey is installed. On Windows, look in Program Files for 'Mozilla Firefox' or 'SeaMonkey' folders, or check the application's About dialog.
    Affected if The system has Firefox or SeaMonkey installed on Windows
  2. Check Firefox version on Windows
    For Firefox: Click Help > About Mozilla Firefox, or check the version in the application executable properties, or run 'firefox -v' from command line if available.
    Affected if Firefox version is 3.6.x before 3.6.14, or 3.5.x before 3.5.17, specifically versions 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
  3. Check SeaMonkey version on Windows
    For SeaMonkey: Click Help > About SeaMonkey, or check the version in the application executable properties.
    Affected if SeaMonkey version is 2.0.11 or lower, or versions 1.0 through 1.1 (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)
  4. Confirm Windows platform
    Verify the operating system is Windows. This vulnerability only affects Windows platforms.
    Affected if The browser is running on Windows (the vulnerability does not affect other operating systems)

A user is affected if they are running Firefox versions 3.6.x before 3.6.14 or 3.5.x before 3.5.17, or SeaMonkey version 2.0.11 or earlier or 1.x, on Windows.

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 affected browsers to Firefox 3.5.17+, 3.6.14+, or SeaMonkey 2.0.12+ respectively. For enterprise environments, deploy the updated versions via patch management systems and verify compliance.

Recommended fix High confidence

Firefox 3.6.14 or later (or Firefox 3.5.17 for 3.5.x branch); SeaMonkey 2.0.12 or later

  1. Check the current installed version of Firefox or SeaMonkey from the Help > About menu
  2. Navigate to the official Mozilla Firefox download page (www.mozilla.org) or SeaMonkey download page
  3. Download Firefox version 3.6.14 or later (or Firefox 3.5.17 if staying on 3.5.x branch), or SeaMonkey version 2.0.12 or later
  4. Close all browser windows and running instances
  5. Run the installer for the downloaded fixed version
  6. Follow the installation wizard prompts to complete the update
  7. Restart the browser after installation completes
  8. Verify the installed version by checking Help > About to confirm the version number matches the fixed release
Caveat These are very old browser versions from 2011; upgrading to these legacy fixed versions may cause compatibility issues with modern websites and web applications; consider migrating to a currently supported browser version (Firefox ESR or current release) for ongoing security support

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-0058 — 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-0058 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