CVE-2011-1059 json
Use-after-free vulnerability in WebCore in WebKit before r77705, as used in Google Chrome before 11.0.672.2 and other products, allows user…
published 2011-02-22 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1074
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
Use-after-free vulnerability in WebCore in WebKit before r77705, as used in Google Chrome before 11.0.672.2 and other products, allows user-assisted remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via vectors that entice a user to resubmit a form, related to improper handling of provisional items by the HistoryController component, aka rdar problem 8938557.
Patch / fix
- google chrome 11.0.672.2
Exploit prediction
1.42% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- code.google.com http://code.google.com/p/chromium/issues/detail?id=70315 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-416 Use After Free
- Technology feeds
References
-
code.google.com
/p/chromium/issues/detail?id=70315
exploit, issue-tracking, patch, vendor-advisory
-
trac.webkit.org
/changeset/77705
patch, third-party-advisory
-
bugs.webkit.org
/show_bug.cgi?id=52819
issue-tracking, patch, third-party-advisory
-
googlechromereleases.blogspot.com
/2011/02/dev-channel-update_17.html
vendor-advisory
-
securityfocus.com
/bid/46577
vdb-entry, third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A13943
vdb-entry, signature, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/65714
vdb-entry
Sources
- CVE List CVE-2011-1059
- NVD CVE-2011-1059
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.