CVE-2017-5064
published 2017-10-27CVE-2017-5064: Incorrect handling of DOM changes in Blink in Google Chrome prior to 58.0.3029.81 for Windows allowed a remote attacker to potentially exploit heap corruption…
PriorityP341high8.8CVSS 3.0
AVNACLPRNUIRSUCHIHAH
EPSS
1.37%
69.3th percentile
Incorrect handling of DOM changes in Blink in Google Chrome prior to 58.0.3029.81 for Windows allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Affected
1 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chrome | < 58.0.3029.81 | 58.0.3029.81 |
CVSS provenance
nvdv3.08.8HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvdv2.06.8MEDIUMAV:N/AC:M/Au:N/C:P/I:P/A:P
osv8.8HIGH
vendor_redhat8.8HIGH
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-5xjr-4x2g-58cf: Incorrect handling of DOM changes in Blink in Google Chrome prior to 58
ghsa_unreviewed·2022-05-14
CVE-2017-5064 [HIGH] CWE-119 GHSA-5xjr-4x2g-58cf: Incorrect handling of DOM changes in Blink in Google Chrome prior to 58
Incorrect handling of DOM changes in Blink in Google Chrome prior to 58.0.3029.81 for Windows allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
OSV
CVE-2017-5064: Incorrect handling of DOM changes in Blink in Google Chrome prior to 58
osv·2017-10-27·CVSS 8.8
CVE-2017-5064 [HIGH] CVE-2017-5064: Incorrect handling of DOM changes in Blink in Google Chrome prior to 58
Incorrect handling of DOM changes in Blink in Google Chrome prior to 58.0.3029.81 for Windows allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Red Hat
chromium-browser: use after free in blink
vendor_redhat·2017-04-19·CVSS 8.8
CVE-2017-5064 [HIGH] chromium-browser: use after free in blink
chromium-browser: use after free in blink
Incorrect handling of DOM changes in Blink in Google Chrome prior to 58.0.3029.81 for Windows allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2017-5064 chromium-browser: use after free in blink
bugzilla·2017-04-20·CVSS 8.8
CVE-2017-5064 [HIGH] CVE-2017-5064 chromium-browser: use after free in blink
CVE-2017-5064 chromium-browser: use after free in blink
An use after free flaw was found in the Blink component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=693974
External References:
https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html
Discussion:
Created chromium tracking bugs for this issue:
Affects: fedora-all [bug 1443852]
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 6 Supplementary
Via RHSA-2017:1124 https://access.redhat.com/errata/RHSA-2017:1124
Bugzilla
CVE-2017-5057 CVE-2017-5058 CVE-2017-5059 CVE-2017-5060 CVE-2017-5061 CVE-2017-5062 CVE-2017-5063 CVE-2017-5064 CVE-2017-5065 CVE-2017-5066 CVE-2017-5067 CVE-2017-5069 chromium: various flaws [fedora-
bugzilla·2017-04-20·CVSS 8.8
CVE-2017-5057 [HIGH] CVE-2017-5057 CVE-2017-5058 CVE-2017-5059 CVE-2017-5060 CVE-2017-5061 CVE-2017-5062 CVE-2017-5063 CVE-2017-5064 CVE-2017-5065 CVE-2017-5066 CVE-2017-5067 CVE-2017-5069 chromium: various flaws [fedora-
CVE-2017-5057 CVE-2017-5058 CVE-2017-5059 CVE-2017-5060 CVE-2017-5061 CVE-2017-5062 CVE-2017-5063 CVE-2017-5064 CVE-2017-5065 CVE-2017-5066 CVE-2017-5067 CVE-2017-5069 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 CV
http://www.securityfocus.com/bid/97939http://www.securitytracker.com/id/1038317https://access.redhat.com/errata/RHSA-2017:1124https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.htmlhttps://crbug.com/693974https://security.gentoo.org/glsa/201705-02http://www.securityfocus.com/bid/97939http://www.securitytracker.com/id/1038317https://access.redhat.com/errata/RHSA-2017:1124https://chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.htmlhttps://crbug.com/693974https://security.gentoo.org/glsa/201705-02
2017-10-27
Published