CVE-2009-1412
What it is
Argument injection vulnerability in the chromehtml: protocol handler in Google Chrome before 1.0.154.59, when invoked by Internet Explorer, allows remote attackers to determine the existence of files, and open tabs for URLs that do not satisfy the IsWebSafeScheme restriction, via a web page that sets document.location to a chromehtml: value, as demonstrated by use of a (1) javascript: or (2) data: URL. NOTE: this can be leveraged for Universal XSS by exploiting certain behavior involving persistence across page transitions.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of data exposure.
- Exploit odds
- 1.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 1.2% in the next 30 days (EPSS).
- Severity: 7.8 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.2% · EPSS, next 30 days
- Weakness
- CWE-200 · Information exposure
- Record status
- Modified
Affected
- Google Chrome ≤ 1.0.154.53
- Google Chrome 0.2.149.29
- Google Chrome 0.2.149.30
- Google Chrome 0.2.152.1
- Google Chrome 0.2.153.1
- Google Chrome 0.3.154.0
- Google Chrome 0.3.154.3
- Google Chrome 0.4.154.18
Attack profile CVSS 2.0 · 7.8
- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- None
- Availability
- None
Raw vector
AV:N/AC:L/Au:N/C:C/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2009-1412.md and follow it. Check whether this project is affected by CVE-2009-1412. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://chromium.googlecode.com/issues/attachment?aid=5579180911289877192&name=Google+Chrome+Advisory.doc
- http://chromium.googlecode.com/issues/attachment?aid=5579180911289877192&name=Google+Chrome+Advisory.doc
References
- http://chromium.googlecode.com/issues/attachment?aid=5579180911289877192&name=Google+Chrome+Advisory.doc
- http://code.google.com/p/chromium/issues/detail?id=9860
- http://googlechromereleases.blogspot.com/2009/04/stable-update-security-fix.html
- https://exchange.xforce.ibmcloud.com/vulnerabilities/50449
- http://chromium.googlecode.com/issues/attachment?aid=5579180911289877192&name=Google+Chrome+Advisory.doc
- http://code.google.com/p/chromium/issues/detail?id=9860
- http://googlechromereleases.blogspot.com/2009/04/stable-update-security-fix.html
- https://exchange.xforce.ibmcloud.com/vulnerabilities/50449