Debian LinuxOperating system · Debian
CVE-2016-1649
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 · uneditedThe Program::getUniformInternal function in Program.cpp in libANGLE, as used in Google Chrome before 49.0.2623.108, does not properly handle a certain data-type mismatch, which allows remote attackers to cause a denial of service (buffer overflow) or possibly have unspecified other impact via crafted shader stages.
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 confidenceBuffer overflow vulnerability in libANGLE's Program::getUniformInternal function in Program.cpp due to improper handling of data-type mismatch, allowing remote attackers to cause denial of service or potentially achieve unspecified impact via crafted shader stages.
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
= 8.0
Ubuntu LinuxOperating system
= 14.04= 15.10= 16.04
ChromeWeb browser
<= 49.0.2623.95= 13.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 Google Chrome versionOpen Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' or 'chromium --version' in terminalAffected if Version is 49.0.2623.95 or lower (any version up to and including 49.0.2623.95)
-
Verify libANGLE library version on Linux systemsRun 'dpkg -l | grep libangle' (Debian/Ubuntu) or 'rpm -qa | grep libangle' (OpenSUSE) to list installed libANGLE packagesAffected if The libangle library package version corresponds to the vulnerable Chrome release (49.0.2623.95 or earlier)
-
Check if Chrome is installed via package managerRun 'dpkg -l | grep -i chrome' on Debian/Ubuntu or check the package version with 'apt-cache policy google-chrome-stable'Affected if The installed google-chrome-stable package version is 49.0.2623.95-1 or earlier
-
Identify libANGLE library file directlyLocate the libANGLE library with 'find /usr -name "*libANGLE*" 2>/dev/null' and check its metadata or associated packageAffected if The library file exists and originates from a Chrome version <= 49.0.2623.95
A user is affected if they are running Google Chrome or a Chromium-based browser version 49.0.2623.95 or earlier, or have libANGLE libraries from that vulnerable version installed on their system.
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.
From vendor dataUpdate Google Chrome to version 49.0.2623.108 or later, which includes the patched libANGLE library with proper type checking in the uniform handling code.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1649 — 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-2016-1649 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