CVE-2017-5380
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 · uneditedA potential use-after-free found through fuzzing during DOM manipulation of SVG content. 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 confidenceA use-after-free vulnerability in Firefox, Firefox ESR, and Thunderbird allows remote code execution through crafted SVG content that exploits improper memory management during DOM manipulation operations.
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= 9.0= 5.0= 6.0= 7.0= 5.0= 6.0= 7.0= 5.0= 6.0= 7.0= 7.3= 7.4= 7.3= 7.4= 7.5= 5.0= 6.0= 7.0< 51.0< 45.7.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Mozilla productRun 'firefox --version' for Firefox, 'firefox-esr --version' for Firefox ESR, or 'thunderbird --version' for Thunderbird. On Red Hat/Debian systems, check installed packages with 'rpm -qa | grep -i firefox' or 'dpkg -l | grep -i firefox'Affected if The product is Firefox, Firefox ESR, or Thunderbird and the version is unpatched
-
Determine Firefox versionIf Firefox is installed, run 'firefox --version' and note the exact version numberAffected if Version is below 51.0 (for example, 50.0, 50.1, etc.)
-
Determine Firefox ESR versionIf Firefox ESR is installed, run 'firefox-esr --version' and note the exact version numberAffected if Version is below 45.7.0 (for example, 45.6.0, 45.5.0, etc.)
-
Check Red Hat or Debian package versionsOn Red Hat systems, run 'rpm -qa | grep -E "firefox|thunderbird"' to list installed Mozilla package versions. On Debian systems, run 'dpkg -l | grep -E "firefox|thunderbird"'Affected if The installed package version corresponds to an unpatched release (for Red Hat: versions before the fixed RHSA/advisory; for Debian: version 9.0 specifically)
A user is affected if they have Firefox below 51.0, Firefox ESR below 45.7.0, or Thunderbird below 45.7.0 installed, or if their OS-level package manager shows unpatched versions from the affected Red Hat or Debian releases.
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 · scoped45.7.051.0
Upgrade to Firefox 51 or later, Firefox ESR 45.7 or later, or Thunderbird 45.7 or later to address the memory corruption flaw.
Firefox 51.0+, Firefox ESR 45.7+, or Thunderbird 45.7+
- 1. Identify the affected application (Firefox, Firefox ESR, or Thunderbird) installed on the system
- 2. For Debian Linux 9.0: Update the package repository and upgrade the affected package (e.g., apt-get update && apt-get upgrade firefox-esr or thunderbird)
- 3. For Enterprise Linux (RHEL/CentOS): Use yum or dnf to update (e.g., yum update firefox or yum update thunderbird)
- 4. Alternatively, download the latest stable version directly from the official Mozilla website: https://www.mozilla.org/
- 5. Restart the application after upgrading
- 6. 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.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5380 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-5380 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