CVE-2016-5172
published 2016-09-25CVE-2016-5172: The parser in Google V8, as used in Google Chrome before 53.0.2785.113, mishandles scopes, which allows remote attackers to obtain sensitive information from…
PriorityP430medium6.5CVSS 3.1
AVNACLPRNUIRSUCHINAN
EPSS
1.86%
77.2th percentile
The parser in Google V8, as used in Google Chrome before 53.0.2785.113, mishandles scopes, which allows remote attackers to obtain sensitive information from arbitrary memory locations via crafted JavaScript code.
Affected
4 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | debian_linux | — | — |
| chrome | <= 53.0.2785.101 | — | |
| nodejs | node.js | 6.0.0 – 6.8.1 | — |
CVSS provenance
nvdv3.16.5MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:P/I:N/A:N
osv8.8HIGH
vendor_ubuntu8.8HIGH
vendor_redhat6.5MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-9g2q-xpx4-5592: The parser in Google V8, as used in Google Chrome before 53
ghsa_unreviewed·2022-05-14
CVE-2016-5172 [MEDIUM] CWE-200 GHSA-9g2q-xpx4-5592: The parser in Google V8, as used in Google Chrome before 53
The parser in Google V8, as used in Google Chrome before 53.0.2785.113, mishandles scopes, which allows remote attackers to obtain sensitive information from arbitrary memory locations via crafted JavaScript code.
OSV
oxide-qt vulnerabilities
osv·2016-10-07·CVSS 8.8
CVE-2016-5170 [HIGH] oxide-qt vulnerabilities
oxide-qt vulnerabilities
A use-after-free was discovered in the V8 bindings in Blink. If a user
were tricked in to opening a specially crafted website, an attacker could
potentially exploit this to cause a denial of service via application
crash, or execute arbitrary code. (CVE-2016-5170)
A use-after-free was discovered in the V8 bindings in Blink. If a user
were tricked in to opening a specially crafted website, an attacker could
potentially exploit this to cause a denial of service via application
crash, or execute arbitrary code. (CVE-2016-5171)
An issue was discovered in V8. If a user were tricked in to opening a
specially crafted website, an attacker could potentially exploit this to
ontain sensitive information from arbitrary memory locations.
(CVE-2016-5172)
Multiple security is
OSV
CVE-2016-5172: The parser in Google V8, as used in Google Chrome before 53
osv·2016-09-25·CVSS 6.5
CVE-2016-5172 [MEDIUM] CVE-2016-5172: The parser in Google V8, as used in Google Chrome before 53
The parser in Google V8, as used in Google Chrome before 53.0.2785.113, mishandles scopes, which allows remote attackers to obtain sensitive information from arbitrary memory locations via crafted JavaScript code.
Ubuntu
Oxide vulnerabilities
vendor_ubuntu·2016-10-07·CVSS 8.8
CVE-2016-5170 [HIGH] Oxide vulnerabilities
Title: Oxide vulnerabilities
Summary: Several security issues were fixed in Oxide.
A use-after-free was discovered in the V8 bindings in Blink. If a user
were tricked in to opening a specially crafted website, an attacker could
potentially exploit this to cause a denial of service via application
crash, or execute arbitrary code. (CVE-2016-5170)
A use-after-free was discovered in the V8 bindings in Blink. If a user
were tricked in to opening a specially crafted website, an attacker could
potentially exploit this to cause a denial of service via application
crash, or execute arbitrary code. (CVE-2016-5171)
An issue was discovered in V8. If a user were tricked in to opening a
specially crafted website, an attacker could potentially exploit this to
ontain sensitive information from arbitr
Red Hat
chromium-browser: arbitrary memory read in v8
vendor_redhat·2016-09-13·CVSS 6.5
CVE-2016-5172 [MEDIUM] chromium-browser: arbitrary memory read in v8
chromium-browser: arbitrary memory read in v8
The parser in Google V8, as used in Google Chrome before 53.0.2785.113, mishandles scopes, which allows remote attackers to obtain sensitive information from arbitrary memory locations via crafted JavaScript code.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2016-5172 chromium-browser: arbitrary memory read in v8
bugzilla·2016-09-14·CVSS 6.5
CVE-2016-5172 [MEDIUM] CVE-2016-5172 chromium-browser: arbitrary memory read in v8
CVE-2016-5172 chromium-browser: arbitrary memory read in v8
An arbitrary memory read flaw was found in the v8 component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=616386
External References:
https://googlechromereleases.blogspot.com/2016/09/stable-channel-update-for-desktop_13.html
Discussion:
Created chromium tracking bugs for this issue:
Affects: fedora-all [bug 1375871]
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 6 Supplementary
Via RHSA-2016:1905 https://rhn.redhat.com/errata/RHSA-2016-1905.html
---
chromium-53.0.2785.113-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.
Bugzilla
CVE-2016-5170 CVE-2016-5171 CVE-2016-5172 CVE-2016-5173 CVE-2016-5174 CVE-2016-5175 chromium: various flaws [fedora-all]
bugzilla·2016-09-14·CVSS 8.8
CVE-2016-5170 [HIGH] CVE-2016-5170 CVE-2016-5171 CVE-2016-5172 CVE-2016-5173 CVE-2016-5174 CVE-2016-5175 chromium: various flaws [fedora-all]
CVE-2016-5170 CVE-2016-5171 CVE-2016-5172 CVE-2016-5173 CVE-2016-5174 CVE-2016-5175 chromium: various flaws [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE: this is
http://rhn.redhat.com/errata/RHSA-2016-1905.htmlhttp://www.debian.org/security/2016/dsa-3667http://www.securityfocus.com/bid/92942http://www.securitytracker.com/id/1036826https://codereview.chromium.org/2077283004https://crbug.com/616386https://googlechromereleases.blogspot.com/2016/09/stable-channel-update-for-desktop_13.htmlhttps://security.gentoo.org/glsa/201610-09http://rhn.redhat.com/errata/RHSA-2016-1905.htmlhttp://www.debian.org/security/2016/dsa-3667http://www.securityfocus.com/bid/92942http://www.securitytracker.com/id/1036826https://codereview.chromium.org/2077283004https://crbug.com/616386https://googlechromereleases.blogspot.com/2016/09/stable-channel-update-for-desktop_13.htmlhttps://security.gentoo.org/glsa/201610-09
2016-09-25
Published