FirefoxWeb browser · Mozilla

CVE-2014-1563

HIGH · 10.0 CVSS v2.0 Published 2014-09-03

Fix available

A fix is available. Upgrade to after 31.1.0 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Use-after-free vulnerability in the mozilla::DOMSVGLength::GetTearOff function in Mozilla Firefox before 32.0, Firefox ESR 31.x before 31.1, and Thunderbird 31.x before 31.1 allows remote attackers to execute arbitrary code or cause a denial of service (heap memory corruption) via an SVG animation with DOM interaction that triggers incorrect cycle collection.

Technical summary

dbcve analysis · high confidence

Use-after-free vulnerability in Mozilla's SVG animation handling (mozilla::DOMSVGLength::GetTearOff) where incorrect cycle collection during DOM interaction causes heap memory to be freed while still referenced, enabling remote code execution or heap corruption.

MitigationUpgrade to Firefox 32.0+, Firefox ESR 31.1+, or Thunderbird 31.1+ to patch this cycle collection flaw in SVG DOM handling.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

FirefoxWeb browser

Affected:<= 31.1.0= 30.0= 31.0

EvergreenOperating system

Affected:= 11.4

OpensuseOperating system

Affected:= 12.3= 13.1

SolarisOperating system

Affected:= 11.3

ThunderbirdApplication

Affected:= 31.0

CVSS breakdown

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?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify the installed Mozilla product

Determine whether the system has Mozilla Firefox or Thunderbird installed. On Linux, check for firefox or thunderbird packages via package manager (dpkg -l, rpm -qa). On Windows, check Program Files for Firefox or Thunderbird directories.

Affected if The product is Mozilla Firefox or Mozilla Thunderbird
Check the installed Firefox version

For Firefox: Run 'firefox --version' from command line, or check Help > About in the GUI, or inspect the version file (e.g., /usr/lib/firefox/version.txt on Linux)

Affected if Version is 30.0, 31.0, or any version <= 31.1.0
Check the installed Thunderbird version

For Thunderbird: Run 'thunderbird --version' from command line, or check Help > About in the GUI, or inspect the version file

Affected if Version is 31.0
Verify SVG support is enabled

In Firefox/Thunderbird, type 'about:config' in address bar, then search for 'svg'. Ensure 'svg.enabled' is set to true (default). Alternatively, visit any webpage with SVG animation to confirm rendering works.

Affected if SVG rendering is enabled (this is the default configuration)
Check OS-level package versions (for Linux distributions)

On openSUSE: run 'rpm -q firefox' or 'rpm -q mozilla-firefox' to get the exact package version. On openSUSE 11.4, 12.3, or 13.1, the Firefox package version indicates the vulnerability.

Affected if Running openSUSE 11.4, 12.3, or 13.1 with Firefox versions matching the affected ranges

You are affected if you run Mozilla Firefox <= 31.1.0 (including 30.0 and 31.0) or Thunderbird 31.0, with SVG support enabled (default), on any supported platform.

Generated from the published advisory. Verify against your own configuration.

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 31.1.0

Interim mitigation

Upgrade to Firefox 32.0+, Firefox ESR 31.1+, or Thunderbird 31.1+ to patch this cycle collection flaw in SVG DOM handling.

Recommended fix High confidence

Firefox 32.0+, Firefox ESR 31.1+, Thunderbird 31.1+

Update Mozilla Firefox to version 32.0 or later
Update Mozilla Firefox ESR to version 31.1 or later
Update Mozilla Thunderbird to version 31.1 or later
After updating, restart the application to apply the changes

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
Testing6.0 h
Review / QA2.0 h

14.0 hours of engineering $2,380

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-1563 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2014-1563?

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.

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

At a glance

A fix existsUpgrade to after 31.1.0 or later

Severity 10.0 High

Exploit likelihood EPSS, next 30 days 5.8%

Affects: Firefox

Remediation

A high-priority fix

Fix this in Firefox 14 hrs · Moderate

Typical engagement from $2,380

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2014-1563 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References