CVE-2016-1669
What it is
The Zone::New function in zone.cc in Google V8 before 5.0.71.47, as used in Google Chrome before 50.0.2661.102, does not properly determine when to expand certain memory allocations, which allows remote attackers to cause a denial of service (buffer overflow) or possibly have unspecified other impact via crafted JavaScript code.
At a glance
- Exploitability
- Can be exploited over the network without logging in, but needs a user to act. High risk of data exposure, data tampering, service disruption.
- Exploit odds
- 4.3% 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: 4.3% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 4.3% · EPSS, next 30 days
- Weakness
- CWE-119 · Buffer errors
- Record status
- Modified
Affected
- Debian Linux 8.0
- Google Chrome ≤ 50.0.2661.87
- Opensuse 13.1
- Google v8 ≤ 5.0.71
- Nodejs node.js < 0.10.46
- Nodejs node.js < 0.12.15
- Nodejs node.js ≤ 4.1.2
- Nodejs node.js < 4.4.6
Attack profile CVSS 3.1 · 8.8
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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-2016-1669.md and follow it. Check whether this project is affected by CVE-2016-1669. 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://googlechromereleases.blogspot.com/2016/05/stable-channel-update.html
- http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00043.html
- http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00050.html
- http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00048.html
- http://lists.opensuse.org/opensuse-updates/2016-07/msg00063.html
- http://rhn.redhat.com/errata/RHSA-2016-1080.html
- http://rhn.redhat.com/errata/RHSA-2017-0002.html
- http://www.debian.org/security/2016/dsa-3590
- http://www.securityfocus.com/bid/90584
- http://www.securitytracker.com/id/1035872
- http://www.ubuntu.com/usn/USN-2960-1
- https://access.redhat.com/errata/RHSA-2017:0879
- https://access.redhat.com/errata/RHSA-2017:0880
- https://access.redhat.com/errata/RHSA-2017:0881
- https://access.redhat.com/errata/RHSA-2017:0882
- https://access.redhat.com/errata/RHSA-2018:0336
- https://codereview.chromium.org/1945313002
- https://crbug.com/606115
- https://h20566.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c05347541
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CITS5GIUTNWVSUXMSORIAJJLQBEGL2CK/
- https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/ZPTKXI62OPCJCJGCSFMST4HIBQ27J72W/
- https://security.gentoo.org/glsa/201605-02
- http://googlechromereleases.blogspot.com/2016/05/stable-channel-update.html
- http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00043.html
- http://lists.opensuse.org/opensuse-security-announce/2016-05/msg00050.html