ChromeWeb browser · Google
CVE-2016-1633
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 · uneditedUse-after-free vulnerability in Blink, as used in Google Chrome before 49.0.2623.75, allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors.
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 · moderate confidenceA use-after-free vulnerability in the Blink rendering engine allows remote attackers to freed memory after it has been deallocated, potentially enabling code execution or denial of service. The vulnerability exists in Google Chrome versions prior to 49.0.2623.75.
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
<= 48.0.2564.116CVSS 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.
-
Find installed Google Chrome versionOpen Chrome and navigate to chrome://version, or run 'google-chrome --version' (Linux), 'chrome --version' (Windows), or check Help > About Google ChromeAffected if Any version number is returned successfully
-
Compare version to affected rangeExamine the version number displayed. The affected range is any version <= 48.0.2564.116. Versions 49.0.2623.75 and later are patchedAffected if Installed version is 48.0.2564.116 or earlier (any version starting with 48.0.2564.x where x is 116 or lower, or any version prior to 48.x)
-
Confirm Chrome is the active browserVerify that Google Chrome (not Chromium, Edge, or other Chromium-based browsers) is the browser in use. This CVE specifically affects Google ChromeAffected if Google Chrome is in use and the version falls within the affected range
If the installed Google Chrome version is 48.0.2564.116 or any earlier version, the environment is vulnerable to this use-after-free flaw in the Blink rendering engine.
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 · scopedUpdate Google Chrome to version 49.0.2623.75 or later to patch the vulnerability. Organizations should deploy the update through their patch management infrastructure.
Google Chrome 49.0.2623.75 or later (ensure you are on the latest stable release)
- Open Google Chrome and navigate to the menu (three dots) > Help > About Google Chrome
- Verify the current version number. If it shows 48.0.2564.116 or lower, the browser is vulnerable
- Chrome will automatically check for updates; if an update is available, click 'Update Google Chrome'
- Restart the browser to apply the update
- After restart, confirm the version is 49.0.2623.75 or later by returning to Help > About Google Chrome
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1633 — 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-1633 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