CVE-2011-3908 json
Google Chrome before 16.0.912.63 does not properly parse SVG documents, which allows remote attackers to cause a denial of service (out-of-…
published 2011-12-13 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3862
- cvss
- 5.0
- 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 16.0.912.63 does not properly parse SVG documents, which allows remote attackers to cause a denial of service (out-of-bounds read) via unspecified vectors.
Patch / fix
- google chrome 16.0.912.63
- apple itunes 10.6
- apple safari 5.1.4
- apple iphone_os 5.1
- 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
1.75% 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 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-125 Out-of-bounds Read
- Technology feeds
References
-
lists.apple.com
/archives/security-announce/2012/Mar/msg00003.html
vendor-advisory
-
lists.apple.com
/archives/security-announce/2012/Mar/msg00000.html
vendor-advisory
-
lists.apple.com
/archives/security-announce/2012/Mar/msg00001.html
vendor-advisory
-
securitytracker.com
/id?1026774
vdb-entry
- googlechromereleases.blogspot.com /2011/12/stable-channel-update.html
- code.google.com /p/chromium/issues/detail?id=100863
-
secunia.com
/advisories/48377
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/73807
vdb-entry
-
secunia.com
/advisories/48274
third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A14791
vdb-entry, signature
-
secunia.com
/advisories/48288
third-party-advisory
Sources
- CVE List CVE-2011-3908
- NVD CVE-2011-3908
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.