FirefoxWeb browser · Mozilla

CVE-2015-2710

MEDIUM · 6.8 CVSS v2.0 Published 2015-05-14

Fix available

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

See remediation →

77/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Heap-based buffer overflow in the SVGTextFrame class in Mozilla Firefox before 38.0, Firefox ESR 31.x before 31.7, and Thunderbird before 31.7 allows remote attackers to execute arbitrary code via crafted SVG graphics data in conjunction with a crafted Cascading Style Sheets (CSS) token sequence.

Technical summary

dbcve analysis · high confidence

A heap-based buffer overflow vulnerability exists in the SVGTextFrame class of Mozilla Firefox (before 38.0), Firefox ESR (before 31.7), and Thunderbird (before 31.7). The flaw is triggered when processing specially crafted SVG graphics data combined with a malicious Cascading Style Sheets (CSS) token sequence, potentially allowing remote attackers to execute arbitrary code.

MitigationApply vendor-supplied security updates to the affected products (Firefox 38.0+, Firefox ESR 31.7+, Thunderbird 31.7+). As this vulnerability has public exploit potential for code execution, prioritize patching based on organizational risk assessment.

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.0= 31.1.0= 31.1.1= 31.3.0= 31.5.1= 31.5.2= 31.5.3<= 37.0.2

Firefox EsrWeb browser

Affected:= 31.1= 31.2= 31.3= 31.4= 31.5= 31.6.0

ThunderbirdApplication

Affected:<= 31.5

Suse Linux Enterprise Software Development KitApplication

Affected:= 12.0

Suse Linux Enterprise DesktopOperating system

Affected:= 12.0

Suse Linux Enterprise ServerOperating system

Affected:= 12.0

OpensuseOperating system

Affected:= 13.1= 13.2

CVSS breakdown

From the vector

Attack vector: Network
Complexity: M
Authentication: None
Confidentiality: Partial
Integrity: Partial
Availability: Partial

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

Am I affected?

dbcve checks

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

Identify the installed Mozilla product and version

Open the application and navigate to Help > About (Firefox/Thunderbird) or check the package manager for the installed version

Affected if The product is Firefox, Firefox ESR, or Thunderbird with a version lower than 38.0 for Firefox, lower than 31.7 for ESR/Thunderbird, or matching any of the specific affected versions listed (31.0, 31.1.0, 31.1.1, 31.3.0, 31.5.1-31.5.3, 37.0.2 or earlier for Firefox; 31.1-31.6.0 for ESR; 31.5 or earl
Confirm the product type

Determine if the installation is standard Firefox, Firefox ESR (Extended Support Release), or Thunderbird by checking the application name or about dialog

Affected if The installed product is Firefox ESR or Thunderbird at any version below 31.7, or standard Firefox below 38.0
Verify SVG rendering capability is present

The vulnerability exists in the SVGTextFrame class which handles SVG graphics rendering. This component is present in all standard Firefox/Thunderbird installations with SVG support enabled

Affected if SVG rendering is enabled (default state) and the version is within the affected range

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

Remediation

From vendor data

Upgrade available Upgrade to a release after 37.0.2

Interim mitigation

Apply vendor-supplied security updates to the affected products (Firefox 38.0+, Firefox ESR 31.7+, Thunderbird 31.7+). As this vulnerability has public exploit potential for code execution, prioritize patching based on organizational risk assessment.

Fix this in Firefox Scoped from the published advisory

Consultation2.0 h
Implementation3.0 h
Testing4.0 h
Review / QA2.0 h

11.0 hours of engineering $1,900

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,040.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2015-2710 — 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-2015-2710 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2015-2710?

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 37.0.2 or later

Severity 6.8 Medium

Exploit likelihood EPSS, next 30 days 4.8%

Affects: Firefox

Remediation

A high-priority fix

Fix this in Firefox 11 hrs · Moderate

Typical engagement from $1,900

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2015-2710 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