FirefoxWeb browser · Mozilla
CVE-2017-5377
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 memory corruption vulnerability in Skia that can occur when using transforms to make gradients, resulting in a potentially exploitable crash. This vulnerability affects 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 memory corruption vulnerability exists in the Skia graphics library used by Firefox. The flaw occurs when processing transforms to create gradients, which can cause a crash that may potentially be exploitable for code execution. This client-side vulnerability affects Firefox installations prior to version 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
FirefoxWeb browser
< 51.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.
-
Check installed Firefox versionOpen Firefox, click the menu button (three horizontal lines), select Help, then About Firefox. The version number will display in the window that opens. Alternatively, type 'about:support' in the address bar and locate the Version field under Application Basics.Affected if The displayed version is less than 51.0 (for example, 50.0, 50.0.1, 49.x, etc.)
-
Confirm version via command lineOn Windows, open Command Prompt and run: 'reg query "HKLM\SOFTWARE\Mozilla\Mozilla Firefox" /v CurrentVersion'. On macOS, run: '/Applications/Firefox.app/Contents/MacOS/firefox --version'. On Linux, run: 'firefox --version'.Affected if The reported version number is below 51.0
-
Identify Firefox release channelIn Firefox, navigate to 'about:support' and locate the 'Update Channel' entry under Application Basics. This shows whether you are on Stable, Beta, or Nightly.Affected if You are on a channel receiving updates for versions prior to 51.0 and have not manually updated
You are affected if your installed Firefox version is below 51.0, as the memory corruption flaw in the Skia library exists only in those earlier versions.
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 · scoped51.0
Update Firefox to version 51 or later to patch the memory corruption vulnerability in the Skia library. Organizations should deploy the browser update across all affected systems.
Firefox 51.0 or later
- Check the current Firefox version by navigating to Help > About Firefox
- Update Firefox to version 51.0 or later by using the built-in update feature (Help > About Firefox > Update) or downloading the latest version from the official Mozilla website
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Firefox
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5377 — 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-5377 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