CVE-2016-1701
What it is
The Autofill implementation in Google Chrome before 51.0.2704.79 mishandles the interaction between field updates and JavaScript code that triggers a frame deletion, which allows remote attackers to cause a denial of service (use-after-free) or possibly have unspecified other impact via a crafted web site, a different vulnerability than CVE-2016-1690.
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
- 0.9% 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: 0.9% in the next 30 days (EPSS).
- Severity: 8.8 HIGH (CVSS).
- Fix: none linked yet, which raises it.
Details
- Published
- Last modified
- Exploit probability
- 0.9% · EPSS, next 30 days
- Record status
- Modified
Affected
- Google Chrome ≤ 51.0.2704.63
- Debian Linux 8.0
- Opensuse Leap 42.1
- Opensuse 13.2
- Redhat Enterprise Linux Desktop 6.0
- Redhat Enterprise Linux Server 6.0
- Redhat Enterprise Linux Workstation 6.0
- Suse Linux Enterprise 12.0
Attack profile CVSS 3.0 · 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.0/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-1701.md and follow it. Check whether this project is affected by CVE-2016-1701. 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/06/stable-channel-update.html
- http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00003.html
- http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00004.html
- http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00005.html
- http://www.debian.org/security/2016/dsa-3594
- http://www.securitytracker.com/id/1036026
- https://access.redhat.com/errata/RHSA-2016:1201
- https://codereview.chromium.org/1960023002
- https://crbug.com/608101
- http://googlechromereleases.blogspot.com/2016/06/stable-channel-update.html
- http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00003.html
- http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00004.html
- http://lists.opensuse.org/opensuse-security-announce/2016-06/msg00005.html
- http://www.debian.org/security/2016/dsa-3594
- http://www.securitytracker.com/id/1036026
- https://access.redhat.com/errata/RHSA-2016:1201
- https://codereview.chromium.org/1960023002
- https://crbug.com/608101