CVE-2011-1451
Google Chrome before 11.0.696.57 does not properly handle DOM id maps, which allows remote...
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."
Exploit likelihood
What each source reports
NVD Score used
7.5
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."
- Record
CVE-2011-1451- CVSS 2.0
- 7.5 High
AV:N/AC:L/Au:N/C:P/I:P/A:P - Weakness
- CWE-20
- Updated
- 2026-11-02
CVE List No score
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."
- Record
CVE-2011-1451- Updated
- 2026-11-02
EUVDEUVD-2011-1456 No score
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."
- Record
EUVD-2011-1456- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-69wh-6h58-g8pf No score
Google Chrome before 11.0.696.57 does not properly handle DOM id maps, which allows remote...
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."
- Record
GHSA-69wh-6h58-g8pf- Weakness
- CWE-20
- 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-2011-1451 is a high vulnerability (CVSS 7.5) in Google Chrome, published May 3, 2011. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.82%, the 78th percentile. No source names a fixed version.
References
support.apple.com/kb/HT4981
exchange.xforce.ibmcloud.com/vulnerabilities/67158
lists.apple.com/archives/Security-announce/2011//Oct/msg00001.html
code.google.com/p/chromium/issues/detail?id=77463
lists.apple.com/archives/Security-announce/2011//Oct/msg00000.html
googlechromereleases.blogspot.com/2011/04/chrome-stable-update.html