CVE-2011-3098 json
Google Chrome before 19.0.1084.46 on Windows uses an incorrect search path for the Windows Media Player plug-in, which might allow local us…
published 2012-05-16 14 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3066
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 19%
- public exploits
- 0
- none known
Summary
Google Chrome before 19.0.1084.46 on Windows uses an incorrect search path for the Windows Media Player plug-in, which might allow local users to gain privileges via a Trojan horse plug-in in an unspecified directory.
Patch / fix
- 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
0.27% chance of exploitation in the next 30 days, higher than 19% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
- Technology feeds
References
-
code.google.com
/p/chromium/issues/detail?id=124216
issue-tracking, patch
-
lists.opensuse.org
/opensuse-security-announce/2012-05/msg00017.html
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2012-08/msg00009.html
vendor-advisory, third-party-advisory
-
googlechromereleases.blogspot.com
/2012/05/stable-channel-update.html
vendor-advisory
-
securitytracker.com
/id?1027067
vdb-entry, third-party-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A15618
vdb-entry, signature
-
securityfocus.com
/bid/53540
vdb-entry, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/75603
vdb-entry
Sources
- CVE List CVE-2011-3098
- NVD CVE-2011-3098
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.