CVE-2011-1451 json
Google Chrome before 11.0.696.57 does not properly handle DOM id maps, which allows remote attackers to cause a denial of service or possib…
published 2011-05-03 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1456
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
Google Chrome before 11.0.696.57 does not properly handle DOM id maps, which allows remote attackers to cause a denial of service or possibly have unspecified other impact via unknown vectors that lead to "dangling pointers."
Patch / fix
- google chrome 11.0.696.57
- apple itunes 10.5
- apple safari 5.0.6
- apple iphone_os 5.0
Exploit prediction
1.82% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
- Technology feeds
References
-
lists.apple.com
/archives/Security-announce/2011//Oct/msg00001.html
vendor-advisory, mailing-list, third-party-advisory
-
lists.apple.com
/archives/Security-announce/2011//Oct/msg00000.html
vendor-advisory, mailing-list, third-party-advisory
-
lists.apple.com
/archives/security-announce/2011//Jul/msg00002.html
vendor-advisory, mailing-list, third-party-advisory
-
googlechromereleases.blogspot.com
/2011/04/chrome-stable-update.html
vendor-advisory
-
support.apple.com
/kb/HT4981
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/67158
vdb-entry, third-party-advisory
-
code.google.com
/p/chromium/issues/detail?id=77463
permissions-required
-
support.apple.com
/kb/HT4999
third-party-advisory
-
support.apple.com
/kb/HT4808
third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14279
vdb-entry, signature, third-party-advisory
Sources
- CVE List CVE-2011-1451
- NVD CVE-2011-1451
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.