dbcve.org
FirefoxWeb browser · Mozilla

CVE-2013-0758

HIGH · 9.3 CVSS v2.0 Published 2013-01-13
Fix available
A fix is available. Upgrade to 2.15 / 10.0.12 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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 before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderbird ESR 10.x before 10.0.12 and 17.x before 17.0.2, and SeaMonkey before 2.15 allow remote attackers to execute arbitrary JavaScript code with chrome privileges by leveraging improper interaction between plugin objects and SVG elements.

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

This is a privilege escalation vulnerability in Mozilla products where improper interaction between plugin objects and SVG elements allows arbitrary JavaScript code to execute with chrome (elevated) privileges. An attacker can achieve remote code execution by tricking a user into visiting a malicious web page that exploits this flaw.

MitigationUpgrade affected Mozilla products to Firefox 18.0 or later (ESR 10.0.12+/17.0.2+), Thunderbird 17.0.2 or later (ESR 10.0.12+/17.0.2+), or SeaMonkey 2.15 or later. Alternatively, disable JavaScript or restrict plugin execution as a temporary workaround.

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:< 18.0>= 10.0, < 10.0.12>= 17.0, < 17.0.2
Enterprise Linux DesktopOperating system
Affected:= 5.0= 6.0
Enterprise Linux EusOperating system
Affected:= 5.9= 6.3
Enterprise Linux ServerOperating system
Affected:= 5.0= 6.0
Enterprise Linux Server AusOperating system
Affected:= 5.9
Enterprise Linux WorkstationOperating system
Affected:= 5.0= 6.0
Ubuntu LinuxOperating system
Affected:= 10.04= 11.10= 12.04= 12.10
SeamonkeyApplication
Affected:< 2.15

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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
    Run 'firefox --version' or 'seamonkey --version' to determine which Mozilla browser is installed, or check the package manager (rpm -qa | grep -i firefox or dpkg -l | grep -i firefox)
    Affected if Firefox or SeaMonkey is installed
  2. Check Firefox version
    Run 'firefox --version' or look at Help > About Firefox in the application menu
    Affected if Version is less than 18.0, OR between 10.0 and 10.0.12 (exclusive), OR between 17.0 and 17.0.2 (exclusive)
  3. Check SeaMonkey version
    Run 'seamonkey --version' or look at Help > About SeaMonkey in the application menu
    Affected if Version is less than 2.15
  4. Check system-installed Firefox on RHEL/CentOS
    Run 'rpm -qa | grep -i firefox' to list installed Firefox packages and their versions
    Affected if Firefox package version matches the affected RHEL versions (5.0, 5.9, 6.0, 6.3)
  5. Check system-installed Firefox on Ubuntu/Debian
    Run 'dpkg -l | grep -i firefox' or check the installed package version via 'apt-cache policy firefox'
    Affected if Firefox package version corresponds to Ubuntu 10.04, 11.10, 12.04, or 12.10

Your environment is affected if Firefox version is below 18.0, between 10.0-10.0.12, or between 17.0-17.0.2; or SeaMonkey is below 2.15; or the browser package matches the specific RHEL/Ubuntu versions 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.

dbcve · scoped
Upgrade available Upgrade to 2.15 / 10.0.12 / 17.0.2 or later
Fixed in 2.1510.0.1217.0.2
Interim mitigation

Upgrade affected Mozilla products to Firefox 18.0 or later (ESR 10.0.12+/17.0.2+), Thunderbird 17.0.2 or later (ESR 10.0.12+/17.0.2+), or SeaMonkey 2.15 or later. Alternatively, disable JavaScript or restrict plugin execution as a temporary workaround.

Recommended fix High confidence

Firefox 18.0 (or ESR 10.0.12 / ESR 17.0.2); Seamonkey 2.15

  1. 1. Identify the installed Mozilla Firefox version by navigating to Help > About Firefox
  2. 2. If running Firefox 10.x ESR, upgrade to Firefox ESR 10.0.12 or later
  3. 3. If running Firefox 17.x ESR, upgrade to Firefox ESR 17.0.2 or later
  4. 4. If running Firefox release (non-ESR), upgrade to Firefox 18.0 or later
  5. 5. For Seamonkey users, upgrade to Seamonkey 2.15 or later
  6. 6. Verify the upgrade was successful by checking the version in Help > About
Caveat Minor: Some legacy extensions may not be compatible with newer Firefox versions; users should verify extension compatibility before upgrading

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