dbcve.org
FirefoxWeb browser · Mozilla

CVE-2013-0795

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
The System Only Wrapper (SOW) implementation in Mozilla Firefox before 20.0, Firefox ESR 17.x before 17.0.5, Thunderbird before 17.0.5, Thunderbird ESR 17.x before 17.0.5, and SeaMonkey before 2.17 does not prevent use of the cloneNode method for cloning a protected node, which allows remote attackers to bypass the Same Origin Policy or possibly execute arbitrary JavaScript code with chrome privileges via a crafted web site.

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 System Only Wrapper (SOW) in Mozilla Firefox, Thunderbird, and SeaMonkey fails to block the cloneNode method when used on protected nodes. This allows malicious web pages to clone privileged (chrome-level) objects, bypassing the Same Origin Policy and enabling arbitrary JavaScript execution with elevated privileges.

MitigationUpgrade affected products to Firefox 20.0+, Firefox ESR 17.0.5+, Thunderbird 17.0.5+, Thunderbird ESR 17.0.5+, or SeaMonkey 2.17+ to patch the SOW cloneNode bypass 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:<= 19.0.2= 19.0= 19.0.1= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4
ThunderbirdApplication
Affected:= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4
Thunderbird EsrApplication
Affected:= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4
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. Identify the installed Mozilla product
    Open the application and navigate to Help > About (or check the application name and version in your system installed programs)
    Affected if The product is Firefox, Thunderbird, Thunderbird ESR, or SeaMonkey
  2. Determine the exact version number
    In Help > About, note the version number displayed (for example, Firefox 17.0.4 or SeaMonkey 2.0.9)
    Affected if The version is any of the affected versions listed in the CVE advisory
  3. Compare against affected Firefox versions
    If using Firefox, compare your version to: 17.0 through 17.0.4, 19.0, 19.0.1, or 19.0.2
    Affected if Your Firefox version matches any of these versions
  4. Compare against affected Thunderbird versions
    If using Thunderbird (standard or ESR), compare your version to: 17.0, 17.0.1, 17.0.2, 17.0.3, or 17.0.4
    Affected if Your Thunderbird version matches any of these versions
  5. Compare against affected SeaMonkey versions
    If using SeaMonkey, compare your version to: 2.0 through 2.0.10, or any version 2.17 or lower
    Affected if Your SeaMonkey version is 2.0.x, 2.1-2.16, or 2.17

You are affected if you are running any Firefox version 17.0-17.0.4, 19.0-19.0.2, any Thunderbird/Thunderbird ESR version 17.0-17.0.4, or any SeaMonkey version up to and including 2.17.

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 products to Firefox 20.0+, Firefox ESR 17.0.5+, Thunderbird 17.0.5+, Thunderbird ESR 17.0.5+, or SeaMonkey 2.17+ to patch the SOW cloneNode bypass vulnerability.

Recommended fix High confidence

Upgrade to the first fixed version for your product: Firefox 20.0, Firefox ESR 17.0.5, Thunderbird 17.0.5, Thunderbird ESR 17.0.5, or SeaMonkey 2.17

  1. 1. Identify the currently installed Mozilla product (Firefox, Thunderbird, Thunderbird ESR, or SeaMonkey) and its exact version.
  2. 2. For Firefox users: Upgrade to Firefox 20.0 or later.
  3. 3. For Firefox ESR 17.x users: Upgrade to Firefox ESR 17.0.5 or later.
  4. 4. For Thunderbird users: Upgrade to Thunderbird 17.0.5 or later.
  5. 5. For Thunderbird ESR users: Upgrade to Thunderbird ESR 17.0.5 or later.
  6. 6. For SeaMonkey users: Upgrade to SeaMonkey 2.17 or later.
  7. 7. Verify the upgrade was successful by checking Help > About (or equivalent) to confirm the new version number.
Caveat Standard major version upgrades typically maintain user profile compatibility; ESR versions are designed for stability and extended 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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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