CVE-2013-1735
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 · uneditedUse-after-free vulnerability in the mozilla::layout::ScrollbarActivity function in 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 allows remote attackers to execute arbitrary code via vectors related to image-document scrolling.
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 confidenceA use-after-free vulnerability exists in the mozilla::layout::ScrollbarActivity component in Mozilla Firefox, Thunderbird, SeaMonkey, and their ESR versions. The vulnerability is triggered through scrolling operations in image documents, allowing a remote attacker to free memory that is still being referenced, leading to arbitrary code execution.
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<= 23.0.1= 19.0= 19.0.1= 19.0.2= 20.0= 20.0.1= 21.0= 22.0= 23.0= 17.0= 17.0.1= 17.0.2= 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<= 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<= 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.8CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Mozilla productCheck whether Firefox, Thunderbird, or SeaMonkey is installed by looking at the application name in Add/Remove Programs or by running: firefox --version, thunderbird --version, or seamonkey --versionAffected if Any of these three products are installed
-
Determine Firefox versionIn Firefox, go to Help > About Firefox or enter 'about:support' in the address bar to see the version numberAffected if Version is 23.0.1 or lower, or matches 17.0, 17.0.1, 17.0.2, 19.0, 19.0.1, 19.0.2, 20.0, 20.0.1, 21.0, 22.0, or 23.0
-
Determine Thunderbird versionIn Thunderbird, go to Help > About Thunderbird to see the version numberAffected if Version is 17.0.9 or lower, or matches any of 17.0 through 17.0.8
-
Determine SeaMonkey versionIn SeaMonkey, go to Help > About SeaMonkey to see the version numberAffected if Version is 2.20 or lower, or matches any of 2.0 through 2.0.10
-
Verify trigger condition - image document viewingThe vulnerability is triggered specifically when scrolling within an image document (such as a large image opened directly in the browser). Check if users in your environment open images directly in the browser rather than in external viewersAffected if Users view image documents directly in the browser and scroll through them
Your environment is affected if any installed Mozilla product matches the version ranges above AND users view and scroll through image documents directly in the browser.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade affected products to Firefox 24.0+, Firefox ESR 17.0.9+, Thunderbird 24.0+, Thunderbird ESR 17.0.9+, or SeaMonkey 2.21+ to patch the vulnerability.
Firefox 24.0+, Firefox ESR 17.0.9+, Thunderbird 24.0+, Thunderbird ESR 17.0.9+, or SeaMonkey 2.21+
- 1. Identify the installed Mozilla product (Firefox, Thunderbird, or SeaMonkey) and current version by checking About/Help menu
- 2. For Firefox: Upgrade to version 24.0 or later
- 3. For Firefox ESR 17.x: Upgrade to version 17.0.9
- 4. For Thunderbird: Upgrade to version 24.0 or later
- 5. For Thunderbird ESR 17.x: Upgrade to version 17.0.9
- 6. For SeaMonkey: Upgrade to version 2.21 or later
- 7. Restart the application after upgrade
- 8. Verify the installed version matches or exceeds the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2013-1735 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- www.mozilla.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.fedoraproject.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- rhn.redhat.com
- rhn.redhat.com
- www.debian.org
- www.securityfocus.com
- www.ubuntu.com
- www.ubuntu.com
- bugzilla.mozilla.org
- oval.cisecurity.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-1735 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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