Chrome OsOperating system · Google
CVE-2014-1711
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 GPU driver in the kernel in Google Chrome OS before 33.0.1750.152 allows remote attackers to cause a denial of service (out-of-bounds write) 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 vulnerability in the GPU kernel driver in Google Chrome OS before version 33.0.1750.152 allows an out-of-bounds write that can cause denial of service or potentially enable other unspecified impacts. The attack vector is not specified, making precise exploitation details unclear.
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
Chrome OsOperating system
<= 33.0.1750.149= 33.0.1750.2= 33.0.1750.5= 33.0.1750.16= 33.0.1750.29= 33.0.1750.51= 33.0.1750.58= 33.0.1750.70= 33.0.1750.93= 33.0.1750.112= 33.0.1750.124CVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Confirm the system runs Chrome OSIdentify the operating system. On a Chromebook, this can be done by checking system information (Settings > About Chrome OS) or running 'cat /etc/lsb-release' in the terminal (crosh).Affected if The system is not running Google Chrome OS (the vulnerability only affects Chrome OS, not Windows, macOS, Linux, or other operating systems).
-
Determine the Chrome OS versionAccess the Chrome OS settings: click the status area (bottom right), select Settings, then click 'About Chrome OS' at the bottom. Alternatively, open crosh (Ctrl+Alt+T) and run 'version' to display the OS version.Affected if Unable to determine the installed version for comparison.
-
Compare against affected version rangesReview the installed version number (format: X.Y.Z) and compare it to the affected ranges: any version <= 33.0.1750.149 OR exactly 33.0.1750.2, 33.0.1750.5, 33.0.1750.16, 33.0.1750.29, 33.0.1750.51, 33.0.1750.58, 33.0.1750.70, 33.0.1750.93, 33.0.1750.112, or 33.0.1750.124.Affected if The installed version falls within the affected ranges listed above.
A user is affected if their Chrome OS version is either less than or equal to 33.0.1750.149, or exactly matches one of the specific affected versions (33.0.1750.2 through 33.0.1750.124), indicating the GPU kernel driver contains the out-of-bounds write vulnerability.
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 dataUpgrade Google Chrome OS to version 33.0.1750.152 or later to patch the GPU driver vulnerability. If Chrome OS is not in use, this vulnerability does not apply.
Fix this in Chrome Os
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1711 — 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-2014-1711 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