dbcve.org
ChromeWeb browser · Google

CVE-2017-5044

MEDIUM · 6.3 CVSS v3.1 Published 2017-04-24
Fix available
A fix is available. Upgrade to after 57.0.2987.100 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Heap buffer overflow in filter processing in Skia in Google Chrome prior to 57.0.2987.98 for Mac, Windows, and Linux and 57.0.2987.108 for Android allowed a remote attacker to perform an out of bounds memory read via a crafted HTML page.

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

Heap buffer overflow vulnerability in Skia's filter processing allows a remote attacker to perform out-of-bounds memory reads via a crafted HTML page, potentially exposing sensitive heap memory contents.

MitigationUpdate Google Chrome to version 57.0.2987.98 or later (57.0.2987.108 for Android) to patch the vulnerability.

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
ChromeWeb browser
Affected:<= 57.0.2987.75<= 57.0.2987.100
Debian LinuxOperating system
Affected:= 8.0= 9.0
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L

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 if Google Chrome is installed
    Navigate to Chrome's about page: open chrome://chrome or go to Help > About Google Chrome. Alternatively, run 'google-chrome --version' or 'google-chrome-stable --version' in terminal.
    Affected if Google Chrome is present on the system
  2. Verify Google Chrome version
    On chrome://chrome page, note the version number displayed. Compare it against the affected versions: 57.0.2987.75 and earlier, or 57.0.2987.100 and earlier.
    Affected if Installed version is 57.0.2987.75 or earlier, or falls between 57.0.2987.76 and 57.0.2987.100 inclusive
  3. Check Debian Linux version
    Run 'cat /etc/debian_version' in terminal to identify the Debian release.
    Affected if Running Debian 8.0 (jessie) or Debian 9.0 (stretch) with vulnerable Chrome/Chromium packages
  4. Check Red Hat Enterprise Linux version
    Run 'cat /etc/redhat-release' or 'cat /etc/os-release' to identify the RHEL release.
    Affected if Running RHEL 6.0 Desktop, Server, or Workstation with vulnerable Skia library packages

A user is affected if they are running Google Chrome version 57.0.2987.75 or earlier (or 57.0.2987.76-100), or if they are on Debian 8.0/9.0 or RHEL 6.0 with vulnerable Skia-based components.

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.

From vendor data
Upgrade available Upgrade to a release after 57.0.2987.100
Interim mitigation

Update Google Chrome to version 57.0.2987.98 or later (57.0.2987.108 for Android) to patch the vulnerability.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing1.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,270
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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