Ubuntu LinuxOperating system · Canonical

CVE-2016-1702

MEDIUM · 6.5 CVSS v3.0 Published 2016-06-05
Fix available
A fix is available. Upgrade to after 51.0.2704.63 or later.
See remediation →
72/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
The SkRegion::readFromMemory function in core/SkRegion.cpp in Skia, as used in Google Chrome before 51.0.2704.79, does not validate the interval count, which allows remote attackers to cause a denial of service (out-of-bounds read) via crafted serialized data.

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

The SkRegion::readFromMemory function in Skia does not validate the interval count from serialized data before processing, allowing an attacker to trigger an out-of-bounds read by providing crafted data with a malformed interval count.

MitigationUpdate Google Chrome to version 51.0.2704.79 or later, or update the Skia library to a version containing the interval count validation fix.

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
Ubuntu LinuxOperating system
Affected:= 14.04= 15.10= 16.04
Debian LinuxOperating system
Affected:= 8.0
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0
ChromeWeb browser
Affected:<= 51.0.2704.63
LeapOperating system
Affected:= 42.1
OpensuseOperating system
Affected:= 13.2

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
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 Google Chrome version
    Navigate to chrome://settings/help or run 'google-chrome --version' in terminal
    Affected if Version is 51.0.2704.63 or lower
  2. Check Skia library version on Debian/Ubuntu
    Run 'dpkg -l | grep skia' or 'apt show libskia-dev' to list installed Skia packages
    Affected if Skia library version from the affected Ubuntu (14.04, 15.10, 16.04) or Debian 8.0 distributions is installed and matches the vulnerable version range
  3. Check Skia library version on RHEL
    Run 'rpm -qa | grep -i skia' to list installed Skia packages
    Affected if Skia library from RHEL 6.0 Desktop, Server, or Workstation is installed and matches the vulnerable version
  4. Check Skia library version on openSUSE
    Run 'rpm -qa | grep -i skia' or check installed packages via YaST
    Affected if Skia library from openSUSE Leap 42.1 or openSUSE 13.2 is installed and matches the vulnerable version
  5. Identify applications using Skia for region deserialization
    Review any custom or third-party applications that process untrusted serialized SkRegion data through Skia's readFromMemory function
    Affected if Any application processes serialized SkRegion data from untrusted sources without additional validation

You are affected if Chrome version is 51.0.2704.63 or lower, or if a Skia library from any of the affected Ubuntu, Debian, RHEL 6.0, or openSUSE versions is installed and processes untrusted serialized region data.

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 51.0.2704.63
Interim mitigation

Update Google Chrome to version 51.0.2704.79 or later, or update the Skia library to a version containing the interval count validation fix.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1702 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1702 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