CVE-2013-6640
What it is
The DehoistArrayIndex function in hydrogen-dehoist.cc (aka hydrogen.cc) in Google V8 before 3.22.24.7, as used in Google Chrome before 31.0.1650.63, allows remote attackers to cause a denial of service (out-of-bounds read) via JavaScript code that sets a variable to the value of an array element with a crafted index.
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
- 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.8% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 1.8% · EPSS, next 30 days
- Weakness
- CWE-119 · Buffer errors
- Record status
- Modified
Affected
- Google Chrome ≤ 31.0.1650.62
- Google Chrome 31.0.1650.0
- Google Chrome 31.0.1650.2
- Google Chrome 31.0.1650.3
- Google Chrome 31.0.1650.4
- Google Chrome 31.0.1650.5
- Google Chrome 31.0.1650.6
- Google Chrome 31.0.1650.7
Attack profile CVSS 2.0 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
Raw vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
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-2013-6640.md and follow it. Check whether this project is affected by CVE-2013-6640. 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://code.google.com/p/v8/source/detail?r=17801
- http://googlechromereleases.blogspot.com/2013/12/stable-channel-update.html
- http://code.google.com/p/v8/source/detail?r=17801
- http://googlechromereleases.blogspot.com/2013/12/stable-channel-update.html
References
- http://code.google.com/p/v8/source/detail?r=17801
- http://googlechromereleases.blogspot.com/2013/12/stable-channel-update.html
- http://lists.opensuse.org/opensuse-updates/2013-12/msg00090.html
- http://lists.opensuse.org/opensuse-updates/2013-12/msg00096.html
- http://lists.opensuse.org/opensuse-updates/2013-12/msg00122.html
- http://lists.opensuse.org/opensuse-updates/2013-12/msg00124.html
- http://lists.opensuse.org/opensuse-updates/2014-01/msg00042.html
- http://lists.opensuse.org/opensuse-updates/2014-01/msg00063.html
- http://secunia.com/advisories/56216
- http://secunia.com/advisories/56217
- http://www.debian.org/security/2013/dsa-2811
- http://www.securitytracker.com/id/1029442
- https://code.google.com/p/chromium/issues/detail?id=319860
- http://code.google.com/p/v8/source/detail?r=17801
- http://googlechromereleases.blogspot.com/2013/12/stable-channel-update.html
- http://lists.opensuse.org/opensuse-updates/2013-12/msg00090.html
- http://lists.opensuse.org/opensuse-updates/2013-12/msg00096.html
- http://lists.opensuse.org/opensuse-updates/2013-12/msg00122.html
- http://lists.opensuse.org/opensuse-updates/2013-12/msg00124.html
- http://lists.opensuse.org/opensuse-updates/2014-01/msg00042.html
- http://lists.opensuse.org/opensuse-updates/2014-01/msg00063.html
- http://secunia.com/advisories/56216
- http://secunia.com/advisories/56217
- http://www.debian.org/security/2013/dsa-2811
- http://www.securitytracker.com/id/1029442