CVE-2019-13768: Use after free in FileAPI
Published Jan 16, 2019
·Updated
Use after free in FileAPI in Google Chrome prior to 72.0.3626.81 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chrome security severity: High)
Credit
Mark Brand(Google Project Zero)
Affected Software
2 affected componentsFixes available
Google Chrome<72.0.3626.81
72.0.3626.81
Google Chrome<72.0.3626.81
Event History
Jan 16, 2019
CVE Published
12:00 AM
Jan 2, 2023
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2019-5754
- CVE-2019-5782
- CVE-2019-5755
- CVE-2019-5756
- CVE-2019-5757
- CVE-2019-5758
- CVE-2019-5759
- CVE-2019-5760
- CVE-2019-5761
- CVE-2019-5762
- CVE-2019-5763
- CVE-2019-5764
- CVE-2019-5765
- CVE-2019-5785
- CVE-2019-5766
- CVE-2019-5767
- CVE-2019-5768
- CVE-2019-5769
- CVE-2019-5770
- CVE-2019-5771
- CVE-2019-5772
- CVE-2019-5773
- CVE-2019-5774
- CVE-2019-5775
- CVE-2019-5776
- CVE-2019-5777
- CVE-2018-20073
- CVE-2019-5778
- CVE-2019-5779
- CVE-2019-5780
- CVE-2019-5783
- CVE-2019-5781
- CVE-2019-13684
Frequently Asked Questions
1
What is the severity of CVE-2019-13768?
The severity of CVE-2019-13768 is classified as High.
2
How do I fix CVE-2019-13768?
To fix CVE-2019-13768, update Google Chrome to version 72.0.3626.81 or later.
3
What does CVE-2019-13768 affect?
CVE-2019-13768 affects Google Chrome versions prior to 72.0.3626.81.
4
What type of vulnerability is CVE-2019-13768?
CVE-2019-13768 is a use after free vulnerability in the FileAPI of Google Chrome.
5
Can CVE-2019-13768 lead to a sandbox escape?
Yes, CVE-2019-13768 allows a remote attacker to potentially perform a sandbox escape via a crafted HTML page.