dbcve.org
FirefoxWeb browser · Mozilla

CVE-2013-0789

HIGH · 10.0 CVSS v2.0 Published 2013-04-03
Fix available
A fix is available. Upgrade to after 19.0.2 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
Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 20.0 and SeaMonkey before 2.17 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via vectors related to the nsContentUtils::HoldJSObjects function and the nsAutoPtr class, and other vectors.

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

Memory corruption vulnerabilities in the Mozilla browser engine (Firefox before 20.0 and SeaMonkey before 2.17) related to the nsContentUtils::HoldJSObjects function and nsAutoPtr class allow remote attackers to cause denial of service via application crash or potentially execute arbitrary code through specially crafted web content.

MitigationUpgrade affected installations to Firefox 20.0 or later, or SeaMonkey 2.17 or later, to resolve the memory corruption vulnerabilities in the browser engine.

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:<= 19.0.2= 19.0= 19.0.1
SeamonkeyApplication
Affected:<= 2.17= 2.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.7= 2.0.8= 2.0.9= 2.0.10

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. Check Firefox version on Windows
    Open Firefox, click the menu button (three horizontal lines), select Help, then About Firefox. The version number is displayed in the window that opens.
    Affected if Version displayed is 19.0, 19.0.1, 19.0.2, or any version lower than 19.0.2 (e.g., 19.0, 18.x, 17.x, etc.)
  2. Check Firefox version on Linux
    Open a terminal and run: firefox --version
    Affected if Version output is 19.0, 19.0.1, 19.0.2, or any version lower than 19.0.2
  3. Check Firefox version on macOS
    Open Firefox, click the Firefox menu, select About Firefox.
    Affected if Version displayed is 19.0, 19.0.1, 19.0.2, or any version lower than 19.0.2
  4. Check SeaMonkey version on Windows
    Open SeaMonkey, click the menu button (or Tools menu in older versions), select About SeaMonkey. The version number is displayed in the window that opens.
    Affected if Version displayed is 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4, 2.0.5, 2.0.6, 2.0.7, 2.0.8, 2.0.9, 2.0.10, or any version up to and including 2.17 (e.g., 2.1x, 2.16.x, etc.)
  5. Check SeaMonkey version on Linux
    Open a terminal and run: seamonkey --version
    Affected if Version output matches any of the affected versions listed (2.0.x through 2.17)

You are affected if either Firefox version is 19.0, 19.0.1, 19.0.2, or lower than 19.0.2, OR SeaMonkey version is 2.0.x through 2.17 inclusive.

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 19.0.2
Interim mitigation

Upgrade affected installations to Firefox 20.0 or later, or SeaMonkey 2.17 or later, to resolve the memory corruption vulnerabilities in the browser engine.

Recommended fix High confidence

Firefox 20.0 or later; SeaMonkey 2.17 or later

  1. 1. Determine which affected product is in use: Firefox or SeaMonkey
  2. 2. For Firefox users: Navigate to Help > About Firefox to check the current version
  3. 3. For SeaMonkey users: Navigate to Help > About SeaMonkey to check the current version
  4. 4. If the installed version is <= 19.0.2 for Firefox, proceed with upgrade
  5. 5. If the installed version is <= 2.17 for SeaMonkey, proceed with upgrade
  6. 6. Download Firefox 20.0 or later from the official Mozilla website (www.mozilla.org)
  7. 7. Alternatively, download SeaMonkey 2.17 or later from the official Mozilla website
  8. 8. Close all browser windows and running instances before upgrading
Caveat Upgrading to newer major versions may affect existing browser extensions or add-ons that are not compatible with the new release

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-2013-0789 — 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-2013-0789 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