CVE-2010-3249
Google Chrome before 6.0.472.53 does not properly implement SVG filters, which allows remote...
Google Chrome before 6.0.472.53 does not properly implement SVG filters, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors, related to a "stale pointer" issue.
Exploit likelihood
What each source reports
NVD Score used
Google Chrome before 6.0.472.53 does not properly implement SVG filters, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors, related to a "stale pointer" issue.
- Record
CVE-2010-3249- CVSS 2.0
- 9.3 High
AV:N/AC:M/Au:N/C:C/I:C/A:C - Updated
- 2026-11-02
CVE List No score
Google Chrome before 6.0.472.53 does not properly implement SVG filters, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors, related to a "stale pointer" issue.
- Record
CVE-2010-3249- Updated
- 2026-11-02
EUVDEUVD-2010-3248 No score
Google Chrome before 6.0.472.53 does not properly implement SVG filters, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors, related to a "stale pointer" issue.
- Record
EUVD-2010-3248- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-6qhc-933h-g668 No score
Google Chrome before 6.0.472.53 does not properly implement SVG filters, which allows remote...
Google Chrome before 6.0.472.53 does not properly implement SVG filters, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors, related to a "stale pointer" issue.
- Record
GHSA-6qhc-933h-g668- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2010-3249 is a high vulnerability (CVSS 9.3) in Google Chrome, published September 7, 2010. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.30%, the 70th percentile. No source names a fixed version.
