Object lifetime issue in Blink in Google Chrome prior to 72.0.3626.121 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page.
Published 2019-06-27 17:15:14
Updated 2025-02-05 13:59:26
Source Chrome
View at NVD,   CVE.org

Products affected by CVE-2019-5786

CVE-2019-5786 is in the CISA Known Exploited Vulnerabilities Catalog

CISA vulnerability name:
Google Chrome Blink Use-After-Free Vulnerability
CISA required action:
Apply updates per vendor instructions.
CISA description:
Google Chrome Blink contains a heap use-after-free vulnerability that allows an attacker to potentially perform out of bounds memory access via a crafted HTML page.
Notes:
https://nvd.nist.gov/vuln/detail/CVE-2019-5786
Added on 2022-05-23 Action due date 2022-06-13

Exploit prediction scoring system (EPSS) score for CVE-2019-5786

90.28%
Probability of exploitation activity in the next 30 days EPSS Score History
~ 100 %
Percentile, the proportion of vulnerabilities that are scored at or less

Metasploit modules for CVE-2019-5786

  • Chrome 72.0.3626.119 FileReader UaF exploit for Windows 7 x86
    Disclosure Date: 2019-03-21
    First seen: 2020-04-26
    exploit/windows/browser/chrome_filereader_uaf
    This exploit takes advantage of a use after free vulnerability in Google Chrome 72.0.3626.119 running on Windows 7 x86. The FileReader.readAsArrayBuffer function can return multiple references to the same ArrayBuffer object, which can be freed and overwritten with spraye

CVSS scores for CVE-2019-5786

Base Score Base Severity CVSS Vector Exploitability Score Impact Score Score Source First Seen
4.3
MEDIUM AV:N/AC:M/Au:N/C:N/I:N/A:P
8.6
2.9
NIST
6.5
MEDIUM CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
2.8
3.6
134c704f-9b21-4f2e-91b3-4a467353bcc0 2025-02-03
6.5
MEDIUM CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
2.8
3.6
NIST

CWE ids for CVE-2019-5786

  • The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
    Assigned by:
    • 134c704f-9b21-4f2e-91b3-4a467353bcc0 (Secondary)
    • nvd@nist.gov (Primary)

References for CVE-2019-5786

Jump to
This web site uses cookies for managing your session, storing preferences, website analytics and additional purposes described in our privacy policy.
By using this web site you are agreeing to CVEdetails.com terms of use!