CVE-2010-1825 in the critical feed json
Use-after-free vulnerability in WebKit, as used in Google Chrome before 6.0.472.59, allows remote attackers to cause a denial of service or…
published 16y ago modified 4mo ago also EUVD-2010-1845
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.3%
- EPSS 2.3% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
Use-after-free vulnerability in WebKit, as used in Google Chrome before 6.0.472.59, allows remote attackers to cause a denial of service or possibly have unspecified other impact via vectors related to nested SVG elements.
Patch / fix
Is CVE-2010-1825 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
2.25% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- code.google.com http://code.google.com/p/chromium/issues/detail?id=51252 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
code.google.com
/p/chromium/issues/detail?id=51252
exploit, patch, vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2011-01/msg00006.html
vendor-advisory, mailing-list, third-party-advisory
-
googlechromereleases.blogspot.com
/2010/09/stable-beta-channel-updates_14.html
vendor-advisory
-
secunia.com
/advisories/43068
third-party-advisory
-
bugs.webkit.org
/show_bug.cgi?id=43587
permissions-required
-
vupen.com
/english/advisories/2011/0212
vdb-entry, third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A7202
vdb-entry, signature, third-party-advisory
Sources
- CVE List CVE-2010-1825
- NVD CVE-2010-1825
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.