dbcve.org
Debian LinuxOperating system · Debian

CVE-2017-5376

CRITICAL · 9.8 CVSS v3.0 Published 2018-06-11
Fix available
A fix is available. Upgrade to 45.7.0 / 51.0 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
Use-after-free while manipulating XSL in XSLT documents. This vulnerability affects Thunderbird < 45.7, Firefox ESR < 45.7, and Firefox < 51.

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

A use-after-free vulnerability exists in Mozilla products when manipulating XSL stylesheets in XSLT documents. The vulnerability allows memory to be freed and then accessed again, potentially enabling arbitrary code execution.

MitigationUpgrade affected products to patched versions: Thunderbird to 45.7+, Firefox ESR to 45.7+, or Firefox to 51+.

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
Debian LinuxOperating system
Affected:= 9.0
Enterprise LinuxOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux DesktopOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux ServerOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux Server AusOperating system
Affected:= 7.3= 7.4
Enterprise Linux Server EusOperating system
Affected:= 7.3= 7.4= 7.5
Enterprise Linux WorkstationOperating system
Affected:= 5.0= 6.0= 7.0
FirefoxWeb browser
Affected:< 51.0< 45.7.0

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Check Firefox version
    Open Firefox, go to Help > About Firefox, or run 'firefox --version' from command line
    Affected if Version is below 45.7.0 or below 51.0 (non-ESR releases)
  2. Check Debian Linux version
    Run 'cat /etc/debian_version' or 'lsb_release -a'
    Affected if Version is 9.0
  3. Check Red Hat Enterprise Linux version
    Run 'cat /etc/redhat-release' or 'hostnamectl'
    Affected if Version is 5.0, 6.0, 7.0, 7.3, 7.4, or 7.5
  4. Identify if XSLT processing is in use
    Check for XSL stylesheets (.xsl, .xslt files) in web content, browser extensions, or locally processed documents; inspect browser console for XSLT-related errors when loading styled content
    Affected if XSL stylesheets are being loaded or processed in Firefox

Environment is affected if Firefox version is below 45.7.0 (ESR) or below 51.0 (non-ESR), or if running Debian 9.0 or RHEL 5.x/6.x/7.x variants with vulnerable Firefox versions and XSLT content is being processed.

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 45.7.0 / 51.0 or later
Fixed in 45.7.051.0
Interim mitigation

Upgrade affected products to patched versions: Thunderbird to 45.7+, Firefox ESR to 45.7+, or Firefox to 51+.

Recommended fix High confidence

Firefox 51.0, Firefox ESR 45.7, or Thunderbird 45.7 (or later stable releases)

  1. 1. Identify which Mozilla product is affected (Firefox, Firefox ESR, or Thunderbird)
  2. 2. For Firefox: Upgrade to version 51.0 or later
  3. 3. For Firefox ESR: Upgrade to version 45.7 or later
  4. 4. For Thunderbird: Upgrade to version 45.7 or later
  5. 5. On Linux systems (Debian, RHEL, CentOS, etc.): Run system package manager update (e.g., apt-get update && apt-get upgrade, or yum update) to obtain vendor-provided security patches
  6. 6. Restart the browser/application after updating
  7. 7. Verify the installed version matches or exceeds the fixed release (Firefox >= 51.0, Firefox ESR >= 45.7, Thunderbird >= 45.7)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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