CVE-2011-3881
What it is
WebKit, as used in Google Chrome before 15.0.874.102 and Android before 4.4, allows remote attackers to bypass the Same Origin Policy and conduct Universal XSS (UXSS) attacks via vectors related to (1) the DOMWindow::clear function and use of a selection object, (2) the Object::GetRealNamedPropertyInPrototypeChain function and use of an __proto__ property, (3) the HTMLPlugInImageElement::allowedToLoadFrameURL function and use of a javascript: URL, (4) incorrect origins for XSLT-generated documents in the XSLTProcessor::createDocumentFromSource function, and (5) improper handling of synchronous frame loads in the ScriptController::executeIfJavaScriptURL function.
At a glance
- Exploitability
- Can be exploited over the network without logging in. Limited direct impact.
- Exploit odds
- 1.8% chance of exploitation in the next 30 days (EPSS).
- Fix
- No patch or advisory is linked yet. Look at mitigations or restrict exposure.
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.8% in the next 30 days (EPSS).
- Severity: 4.3 MEDIUM (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 1.8% · EPSS, next 30 days
- Weakness
- CWE-79 · Cross-site scripting
- Record status
- Modified
Affected
- Google Chrome < 15.0.874.102
- Google Android < 4.4
- Apple Safari < 5.1.4
- Apple Iphone Os < 5.1
Attack profile CVSS 2.0 · 4.3
- Attack vector
- Network
- Complexity
- Medium
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
Raw vector
AV:N/AC:M/Au:N/C:N/I:P/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-2011-3881.md and follow it. Check whether this project is affected by CVE-2011-3881. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
References
- http://code.google.com/p/chromium/issues/detail?id=96047
- http://code.google.com/p/chromium/issues/detail?id=96885
- http://code.google.com/p/chromium/issues/detail?id=98053
- http://code.google.com/p/chromium/issues/detail?id=99512
- http://code.google.com/p/chromium/issues/detail?id=99750
- http://googlechromereleases.blogspot.com/2011/10/chrome-stable-release.html
- http://lists.apple.com/archives/security-announce/2012/Mar/msg00001.html
- http://lists.apple.com/archives/security-announce/2012/Mar/msg00003.html
- http://secunia.com/advisories/48288
- http://secunia.com/advisories/48377
- http://www.rafayhackingarticles.net/2014/10/a-tale-of-another-sop-bypass-in-android.html
- http://www.securitytracker.com/id?1026774
- https://android.googlesource.com/platform/external/webkit/+/109d59bf6fe4abfd001fc60ddd403f1046b117ef
- https://exchange.xforce.ibmcloud.com/vulnerabilities/70959
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A12940
- http://code.google.com/p/chromium/issues/detail?id=96047
- http://code.google.com/p/chromium/issues/detail?id=96885
- http://code.google.com/p/chromium/issues/detail?id=98053
- http://code.google.com/p/chromium/issues/detail?id=99512
- http://code.google.com/p/chromium/issues/detail?id=99750
- http://googlechromereleases.blogspot.com/2011/10/chrome-stable-release.html
- http://lists.apple.com/archives/security-announce/2012/Mar/msg00001.html
- http://lists.apple.com/archives/security-announce/2012/Mar/msg00003.html
- http://secunia.com/advisories/48288
- http://secunia.com/advisories/48377