CVE-2016-1690

8 documents6 sources
Severity
7.5HIGH
EPSS
1.7%
top 17.67%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
8
Google ChromeDebian Debian LinuxOpensuse Leap+5 more
Timeline
PublishedJun 5
Latest updateMay 14

Description

The Autofill implementation in Google Chrome before 51.0.2704.63 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-1701.

CVSS vector

CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:HExploitability: 1.6 | Impact: 5.9

Affected Packages7 packages

▶NVDgoogle/chrome50.0.2661.102
▶Ubuntuchromium-browser< 51.0.2704.79-0ubuntu0.14.04.1.1121+1
▶NVDopensuse/leap42.1

Also affects: Debian Linux 8.0, Linux Enterprise 12.0

🔴Vulnerability Details

3
GHSA
GHSA-8x9h-cmjr-hprf: The Autofill implementation in Google Chrome before 51↗2022-05-14
▶
OSV
CVE-2016-1690: The Autofill implementation in Google Chrome before 51↗2016-06-05
▶
CVEList
CVE-2016-1690: The Autofill implementation in Google Chrome before 51↗2016-06-05
▶

📋Vendor Advisories

2
Red Hat
chromium-browser: use-after-free in autofill↗2016-06-01
▶
Red Hat
chromium-browser: heap use-after-free in autofill↗2016-05-25
▶

💬Community

2
Bugzilla
CVE-2016-1690 chromium-browser: heap use-after-free in autofill↗2016-05-26
▶
Bugzilla
CVE-2016-2116 jasper: memory leak in jas_iccprof_createfrombuf()↗2016-03-03
▶