dbcve.org
Chrome OsOperating system · Google

CVE-2014-3188

HIGH · 10.0 CVSS v2.0 Published 2014-10-08
Fix available
A fix is available. Upgrade to after 38.0.2125.77 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Google Chrome before 38.0.2125.101 and Chrome OS before 38.0.2125.101 do not properly handle the interaction of IPC and Google V8, which allows remote attackers to execute arbitrary code via vectors involving JSON data, related to improper parsing of an escaped index by ParseJsonObject in json-parser.h.

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 confidence

Google Chrome and Chrome OS before 38.0.2125.101 contain a vulnerability in the JSON parser (json-parser.h) where ParseJsonObject improperly parses escaped indices when processing JSON data, combined with improper IPC and V8 interaction. This allows remote attackers to execute arbitrary code via crafted JSON data.

MitigationUpgrade to Chrome/Chrome OS version 38.0.2125.101 or later, or ensure automatic updates are enabled to receive the patched version.

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
Affected:<= 38.0.2125.77
ChromeWeb browser
Affected:<= 38.0.2125.7
Enterprise Linux Desktop SupplementaryOperating system
Affected:= 6.0
Enterprise Linux Server SupplementaryOperating system
Affected:= 6.0
Enterprise Linux Server Supplementary EusOperating system
Affected:= 6.6.z
Enterprise Linux Workstation SupplementaryOperating system
Affected:= 6.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Chrome browser version on Linux
    Open Chrome, click Menu > Help > About Google Chrome, or run 'google-chrome --version' in terminal
    Affected if Version is 38.0.2125.7 or earlier
  2. Check Chrome version on Windows or Mac
    Open Chrome, click Menu > Help > About Google Chrome
    Affected if Version is 38.0.2125.7 or earlier
  3. Check Chrome OS version
    Click system tray, click Settings icon, click About Chrome OS at the bottom of the Settings page
    Affected if Version is 38.0.2125.77 or earlier (the model number shown is less than 8125.101)
  4. Check Chrome installation on RHEL systems
    Run 'rpm -q google-chrome-stable' on Red Hat Enterprise Linux to query the installed package version
    Affected if Package is installed with version 38.0.2125.7 or earlier

A user is affected if their installed Chrome, Chrome OS, or Chrome on RHEL version is at or below the vulnerable versions listed (38.0.2125.7 for Chrome, 38.0.2125.77 for Chrome OS).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 38.0.2125.77
Interim mitigation

Upgrade to Chrome/Chrome OS version 38.0.2125.101 or later, or ensure automatic updates are enabled to receive the patched version.

Recommended fix High confidence

Chrome/Chrome OS 38.0.2125.101 or later

  1. Check current Chrome version by navigating to chrome://settings/help or Help > About Google Chrome
  2. If version displays as 38.0.2125.77 or earlier (Chrome) or 38.0.2125.77 or earlier (Chrome OS), the system is vulnerable
  3. For Chrome: The browser should automatically update; trigger manual update by clicking 'Update Google Chrome' button if available, then restart
  4. For Chrome OS: Run 'chrome://settings/help' and allow system to update, or check for system updates via Settings > About Chrome OS > Check for updates
  5. Verify version after update shows 38.0.2125.101 or later

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Os Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3188 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-3188 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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