CVE-2019-5784
published 2019-06-27CVE-2019-5784: Incorrect handling of deferred code in V8 in Google Chrome prior to 72.0.3626.96 allowed a remote attacker to potentially exploit heap corruption via a crafted…
PriorityP429medium6.5CVSS 3.0
AVNACLPRNUIRSUCNINAH
EPSS
1.57%
72.6th percentile
Incorrect handling of deferred code in V8 in Google Chrome prior to 72.0.3626.96 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chromium | chromium | >= 0 < 72.0.3626.109-1 | 72.0.3626.109-1 |
| chromium | chromium | >= 0 < 72.0.3626.109-1 | 72.0.3626.109-1 |
| chromium | chromium | >= 0 < 72.0.3626.109-1 | 72.0.3626.109-1 |
| chromium | chromium | >= 0 < 72.0.3626.109-1 | 72.0.3626.109-1 |
| debian | chromium | < chromium 72.0.3626.109-1 (bookworm) | chromium 72.0.3626.109-1 (bookworm) |
| chrome | < 72.0.3626.96 | 72.0.3626.96 | |
| chrome | >= unspecified < 72.0.3626.96 | 72.0.3626.96 |
CVSS provenance
nvdv3.06.5MEDIUMCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:N/A:P
osv6.5MEDIUM
vendor_debian6.5MEDIUM
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.
Red Hat
chromium-browser: Inappropriate implementation in V8
vendor_redhat·2019-02-06·CVSS 6.5
CVE-2019-5784 [MEDIUM] chromium-browser: Inappropriate implementation in V8
chromium-browser: Inappropriate implementation in V8
Incorrect handling of deferred code in V8 in Google Chrome prior to 72.0.3626.96 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Debian
CVE-2019-5784: chromium - Incorrect handling of deferred code in V8 in Google Chrome prior to 72.0.3626.96...
vendor_debian·2019·CVSS 6.5
CVE-2019-5784 [MEDIUM] CVE-2019-5784: chromium - Incorrect handling of deferred code in V8 in Google Chrome prior to 72.0.3626.96...
Incorrect handling of deferred code in V8 in Google Chrome prior to 72.0.3626.96 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Scope: local
bookworm: resolved (fixed in 72.0.3626.109-1)
bullseye: resolved (fixed in 72.0.3626.109-1)
forky: resolved (fixed in 72.0.3626.109-1)
sid: resolved (fixed in 72.0.3626.109-1)
trixie: resolved (fixed in 72.0.3626.109-1)
GHSA
GHSA-f2p9-3vx7-g835: Incorrect handling of deferred code in V8 in Google Chrome prior to 72
ghsa_unreviewed·2022-05-24
CVE-2019-5784 [MEDIUM] GHSA-f2p9-3vx7-g835: Incorrect handling of deferred code in V8 in Google Chrome prior to 72
Incorrect handling of deferred code in V8 in Google Chrome prior to 72.0.3626.96 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
OSV
CVE-2019-5784: Incorrect handling of deferred code in V8 in Google Chrome prior to 72
osv·2019-06-27·CVSS 6.5
CVE-2019-5784 [MEDIUM] CVE-2019-5784: Incorrect handling of deferred code in V8 in Google Chrome prior to 72
Incorrect handling of deferred code in V8 in Google Chrome prior to 72.0.3626.96 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-5784 chromium: chromium-browser: Inappropriate implementation in V8 [epel-7]
bugzilla·2019-02-12·CVSS 6.5
CVE-2019-5784 [MEDIUM] CVE-2019-5784 chromium: chromium-browser: Inappropriate implementation in V8 [epel-7]
CVE-2019-5784 chromium: chromium-browser: Inappropriate implementation in V8 [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
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.
Discussion:
Use the following template to for t
Bugzilla
CVE-2019-5784 chromium-browser: Inappropriate implementation in V8
bugzilla·2019-02-12·CVSS 6.5
CVE-2019-5784 [MEDIUM] CVE-2019-5784 chromium-browser: Inappropriate implementation in V8
CVE-2019-5784 chromium-browser: Inappropriate implementation in V8
An inappropriate implementation flaw was found in the V8 component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=915975
External References:
https://chromereleases.googleblog.com/2019/02/stable-channel-update-for-desktop.html
Discussion:
Created chromium tracking bugs for this issue:
Affects: epel-7 [bug 1676530]
Affects: fedora-all [bug 1676529]
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 6 Supplementary
Via RHSA-2019:0396 https://access.redhat.com/errata/RHSA-2019:0396
Bugzilla
CVE-2019-5784 chromium: chromium-browser: Inappropriate implementation in V8 [fedora-all]
bugzilla·2019-02-12·CVSS 6.5
CVE-2019-5784 [MEDIUM] CVE-2019-5784 chromium: chromium-browser: Inappropriate implementation in V8 [fedora-all]
CVE-2019-5784 chromium: chromium-browser: Inappropriate implementation in V8 [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-all.
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 issue affects multiple suppor
2019-06-27
Published