ChromeWeb browser · Google
CVE-2018-6162
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 · uneditedImproper deserialization in WebGL in Google Chrome on Mac prior to 68.0.3440.75 allowed a remote attacker to potentially exploit heap corruption 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 confidenceA deserialization vulnerability in WebGL component of Google Chrome on MacOS allows remote attackers to corrupt heap memory via specially crafted HTML pages, potentially leading to arbitrary code execution.
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
< 68.0.3440.75
Debian LinuxOperating system
= 9.0
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.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
- 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, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/help. Alternatively, run 'google-chrome --version' or 'C:\Program Files\Google\Chrome\Application\chrome.exe --version' in command prompt on Windows.Affected if Version is lower than 68.0.3440.75 (for any operating system where Chrome is installed) or equal to 9.0 on Debian Linux.
-
Verify WebGL is enabled in ChromeNavigate to chrome://settings in the address bar, search for 'WebGL' under Advanced settings, or visit chrome://gpu to check WebGL status under the 'Graphics' section.Affected if WebGL is listed as 'Enabled' or 'Hardware accelerated' - the vulnerability exists in the WebGL component, so it only affects environments where WebGL is active.
-
Confirm operating system is MacOSClick the Apple menu > About This Mac on MacOS, or run 'uname -a' in Terminal. The CVE description specifically targets Google Chrome on MacOS.Affected if Running MacOS with an affected Chrome version below 68.0.3440.75.
-
Check Chromium-based browsers on Linux systemsOn Debian 9.0, run 'dpkg -l | grep chromium' or 'apt list --installed | grep -i chrom'. On RHEL 6.0 systems, check for google-chrome or chromium packages using 'rpm -qa | grep -i chrom'.Affected if Chromium or Google Chrome version is below 68.0.3440.75 on Debian 9.0 or RHEL 6.0.
You are affected if Google Chrome (or Chromium) version is below 68.0.3440.75 AND WebGL is enabled in the browser on MacOS, Debian 9.0, or RHEL 6.0.
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 data68.0.3440.75
Update Google Chrome to version 68.0.3440.75 or later on all Mac systems. In enterprise environments, deploy the update via patch management and verify completion.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6162 — 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-2018-6162 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