Chrome OsOperating system · Google
CVE-2014-1708
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 boot implementation in Google Chrome OS before 33.0.1750.152 does not properly consider file persistence, which allows remote attackers to execute arbitrary code via unspecified 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 confidenceVulnerability in Chrome OS boot implementation before version 33.0.1750.152 where file persistence is not properly considered, allowing remote attackers to execute arbitrary code through unspecified vectors during the boot process.
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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Verify the system is running Chrome OSCheck the operating system - this vulnerability affects Chrome OS specifically. Look for Chrome OS in system information or check chrome://version in the Chrome browser.Affected if The system is not Chrome OS (this CVE only affects Chrome OS)
-
Obtain the Chrome OS versionOpen chrome://version in the Chrome browser and note the Chrome OS version number displayed (e.g., 33.0.1750.x). Alternatively, go to Settings > About Chrome OS.Affected if Cannot determine the Chrome OS version - manual verification may be needed through system settings or boot screen information
-
Compare installed version against affected rangeCheck if the installed version is 33.0.1750.149 or lower, OR exactly matches one of these: 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.124Affected if The installed Chrome OS version falls within the affected list (any version <= 33.0.1750.149 or the specific versions listed)
The system is affected if it runs Chrome OS version 33.0.1750.149 or lower, or any of the specific affected point releases (33.0.1750.2 through 33.0.1750.124), and is NOT running version 33.0.1750.152 or later.
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 Chrome OS to version 33.0.1750.152 or later to patch the boot implementation vulnerability.
Chrome OS 33.0.1750.152 or later
- 1. Check current Chrome OS version by navigating to chrome://settings or the About Chrome OS section in Settings
- 2. Navigate to chrome://settings/help to trigger version check and update detection
- 3. If an update is available, allow Chrome OS to download and install the update
- 4. Restart the device to complete the installation of the fixed version
- 5. Verify the version has been updated to 33.0.1750.152 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome Os
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1708 — 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-1708 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