CVE-2019-5787: Use after free in Canvas
First published: Tue Dec 11 2018(Updated: )
Use-after-garbage-collection in Blink in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Credit: Zhe Jin（金哲），Luyao Liu(刘路遥) Chengdu Security Response Center of Qihoo 360 Technology Co cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/chromium-browser | <73.0.3683.75 | 73.0.3683.75 |
| Google Chrome | <73.0.3683.75 | 73.0.3683.75 |
| Google Chrome | <73.0.3683.75 | |
| SUSE Backports | =sle-15 | |
| openSUSE | =15.0 | |
| openSUSE | =15.1 | |
| openSUSE | =42.3 |
Remedy
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://code.google.com/p/chromium/issues/detail?id=913964
- https://chromereleases.googleblog.com/2019/03/stable-channel-update-for-desktop_12.html (Advisory)
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1688209
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1688208
- https://access.redhat.com/errata/RHSA-2019:0708
- https://bugzilla.redhat.com/show_bug.cgi?id=1688189
- http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00085.html
- https://crbug.com/913964
Peer vulnerabilities
(Found alongside the following vulnerabilities)
Frequently Asked Questions
What is the severity of CVE-2019-5787?
CVE-2019-5787 is classified as a high-severity vulnerability due to the potential for remote code execution.
How do I fix CVE-2019-5787?
To fix CVE-2019-5787, update Google Chrome or Chromium-browser to version 73.0.3683.75 or higher.
What is the impact of CVE-2019-5787?
The impact of CVE-2019-5787 includes possible heap corruption, which could allow attackers to execute arbitrary code on the user's system.
Which versions are affected by CVE-2019-5787?
CVE-2019-5787 affects all versions of Google Chrome and Chromium-browser prior to 73.0.3683.75.
Is there a workaround for CVE-2019-5787?
Currently, the only recommended mitigation for CVE-2019-5787 is to upgrade to the latest version of the browser.
- agent/references
- agent/type
- agent/softwarecombine
- agent/first-publish-date
- agent/remedy
- agent/weakness
- agent/severity
- agent/title
- agent/author
- agent/description
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2019-5787
- agent/software-canonical-lookup
- collector/chrome-releases
- agent/software-canonical-lookup-request
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/nvd-index
- package-manager/redhat
- vendor/google
- canonical/google chrome
- vendor/opensuse
- canonical/suse backports
- version/suse backports/sle-15
- canonical/opensuse
- version/opensuse/15.0
- version/opensuse/15.1
- version/opensuse/42.3