CVE-2010-3258 google chrome: Deserialization of Untrusted Data
google chrome: no CVSS score yet. EPSS 0.9% estimated probability of exploitation activity in the next 30 days.
The sandbox implementation in Google Chrome before 6.0.472.53 does not properly deserialize parameters, which has unspecified impact and remote attack vectors.
- EPSS
- 0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 61st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-502 Deserialization of Untrusted Data
- OWASP Top 10
- A08:2025 Software or Data Integrity Failures
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Patch: http://code.google.com/p/chromium/issues/detail?id=52682
- Vendor advisory: http://code.google.com/p/chromium/issues/detail?id=52682
- Vendor advisory: http://googlechromereleases.blogspot.com/2010/09/stable-and-beta-channel-updates.html
Ask an AI about this CVE
Show the prompt
Explain CVE-2010-3258 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2010-3258?via=ask-ai-copy and https://cve.bz/cve/CVE-2010-3258?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2010-3258 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| google:chrome | before 6.0.472.53 |
Attack patterns (CAPEC)
- CAPEC-586 Object Injection Likelihood: Medium · Severity: High
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.