dbcve.org
FirefoxWeb browser · Mozilla

CVE-2013-1737

MEDIUM · 5.0 CVSS v2.0 Published 2013-09-18
Fix available
A fix is available. Upgrade to after 23.0.1 or later.
See remediation →
59/100
Remediation priority · Elevated
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 24.0, Firefox ESR 17.x before 17.0.9, Thunderbird before 24.0, Thunderbird ESR 17.x before 17.0.9, and SeaMonkey before 2.21 do not properly identify the "this" object during use of user-defined getter methods on DOM proxies, which might allow remote attackers to bypass intended access restrictions via vectors involving an expando object.

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 vulnerability in Mozilla Firefox, Thunderbird, and SeaMonkey allows attackers to bypass access restrictions by exploiting improper 'this' object identification when user-defined getter methods are used on DOM proxies. The issue involves manipulating expando objects (custom properties on DOM elements) to trick the getter into operating on the wrong object context, potentially granting unauthorized access to sensitive properties or methods.

MitigationUpgrade to Firefox 24.0+, Firefox ESR 17.0.9+, Thunderbird 24.0+, Thunderbird ESR 17.0.9+, or SeaMonkey 2.21+ as specified in the vendor advisory.

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:= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4= 17.0.5= 17.0.6= 17.0.7= 17.0.8<= 23.0.1= 19.0= 19.0.1
Thunderbird EsrApplication
Affected:= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4= 17.0.5= 17.0.6= 17.0.7= 17.0.8
SeamonkeyApplication
Affected:<= 2.20= 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
ThunderbirdApplication
Affected:<= 17.0.9= 17.0= 17.0.1= 17.0.2= 17.0.3= 17.0.4= 17.0.5= 17.0.6= 17.0.7= 17.0.8

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
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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 which Mozilla product is installed
    Check the installed application: open Help > About in the application, or run 'firefox --version', 'thunderbird --version', or 'seamonkey --version' from command line. On Windows, check Add/Remove Programs or the executable properties.
    Affected if The product is Firefox, Thunderbird, or SeaMonkey
  2. Determine the installed Firefox version
    Run 'firefox --version' or open Firefox and go to Help > About Firefox. Compare the version number to: 17.0, 17.0.1, 17.0.2, 17.0.3, 17.0.4, 17.0.5, 17.0.6, 17.0.7, 17.0.8, 19.0, 19.0.1, or any version up to and including 23.0.1.
    Affected if The version matches any of the affected Firefox versions listed
  3. Determine the installed Thunderbird version
    Run 'thunderbird --version' or open Thunderbird and go to Help > About Thunderbird. Compare the version number to: 17.0 through 17.0.9 inclusive.
    Affected if The version is 17.0 through 17.0.9 inclusive
  4. Determine the installed SeaMonkey version
    Run 'seamonkey --version' or open SeaMonkey and go to Help > About SeaMonkey. Compare the version number to: 2.0 through 2.0.10 inclusive, or any version up to and including 2.20.
    Affected if The version is 2.0 through 2.0.10 inclusive, or 2.20 or lower
  5. Check if using Thunderbird ESR
    In Thunderbird, check Help > About Thunderbird. The ESR versions affected are 17.0 through 17.0.8 inclusive, matching the Thunderbird ESR entry in the affected versions list.
    Affected if Thunderbird ESR version is 17.0 through 17.0.8

You are affected if the installed product version matches any of the specific Firefox (17.x, 19.x, or up to 23.0.1), Thunderbird (up to 17.0.9), Thunderbird ESR (17.0-17.0.8), or SeaMonkey (2.0-2.0.10 or <=2.20) versions listed in the affected ranges.

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.

From vendor data
Upgrade available Upgrade to a release after 23.0.1
Interim mitigation

Upgrade to Firefox 24.0+, Firefox ESR 17.0.9+, Thunderbird 24.0+, Thunderbird ESR 17.0.9+, or SeaMonkey 2.21+ as specified in the vendor advisory.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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