CVE-2011-3049 json
Google Chrome before 17.0.963.83 does not properly restrict the extension web request API, which allows remote attackers to cause a denial…
published 2012-03-23 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3017
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.1%
- EPSS 2.1% chance of exploitation in 30 days, percentile 81%
- public exploits
- 0
- none known
Summary
Google Chrome before 17.0.963.83 does not properly restrict the extension web request API, which allows remote attackers to cause a denial of service (disrupted system requests) via a crafted extension.
Patch / fix
- google chrome 17.0.963.83
- chromium openSUSE Tumbleweed 55.0.2883.75-3.1
- chromium openSUSE Tumbleweed 113.0.5672.92-1.1
opensuse advisories openSUSE-SU-2024:10171-1openSUSE-SU-2024:12948-1
Exploit prediction
2.08% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Technology feeds
References
-
lists.opensuse.org
/opensuse-security-announce/2012-04/msg00000.html
vendor-advisory, mailing-list, third-party-advisory
-
security.gentoo.org
/glsa/glsa-201203-19.xml
vendor-advisory, third-party-advisory
-
googlechromereleases.blogspot.com
/2012/03/stable-channel-update_21.html
release-notes, vendor-advisory
-
code.google.com
/p/chromium/issues/detail?id=108648
vendor-advisory
-
secunia.com
/advisories/48527
third-party-advisory, not-applicable
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15049
vdb-entry, signature, third-party-advisory
-
securitytracker.com
/id?1026841
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/52674
vdb-entry, third-party-advisory
-
osvdb.org
/80295
vdb-entry, broken-link
-
exchange.xforce.ibmcloud.com
/vulnerabilities/74218
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2011-3049
- NVD CVE-2011-3049
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.