CVE-2019-5831
published 2019-06-27CVE-2019-5831: Object lifecycle issue in V8 in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
PriorityP345high8.8CVSS 3.1
AVNACLPRNUIRSUCHIHAH
EPSS
1.98%
78.3th percentile
Object lifecycle issue in V8 in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Affected
14 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| chromium | chromium | >= 0 < 75.0.3770.80-1 | 75.0.3770.80-1 |
| chromium | chromium | >= 0 < 75.0.3770.80-1 | 75.0.3770.80-1 |
| chromium | chromium | >= 0 < 75.0.3770.80-1 | 75.0.3770.80-1 |
| chromium | chromium | >= 0 < 75.0.3770.80-1 | 75.0.3770.80-1 |
| debian | chromium | < chromium 75.0.3770.80-1 (bookworm) | chromium 75.0.3770.80-1 (bookworm) |
| debian | debian_linux | — | — |
| fedoraproject | fedora | — | — |
| fedoraproject | fedora | — | — |
| chrome | < 75.0.3770.80 | 75.0.3770.80 | |
| chrome | >= unspecified < 75.0.3770.80 | 75.0.3770.80 | |
| opensuse | backports | — | — |
| opensuse | leap | — | — |
| opensuse | leap | — | — |
| opensuse | leap | — | — |
CVSS provenance
nvdv3.18.8HIGHCVSS:3.1/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_debian8.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.
Red Hat
chromium-browser: Incorrect map processing in V8
vendor_redhat·2019-06-04·CVSS 8.8
CVE-2019-5831 [HIGH] chromium-browser: Incorrect map processing in V8
chromium-browser: Incorrect map processing in V8
Object lifecycle issue in V8 in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Debian
CVE-2019-5831: chromium - Object lifecycle issue in V8 in Google Chrome prior to 75.0.3770.80 allowed a re...
vendor_debian·2019·CVSS 8.8
CVE-2019-5831 [HIGH] CVE-2019-5831: chromium - Object lifecycle issue in V8 in Google Chrome prior to 75.0.3770.80 allowed a re...
Object lifecycle issue in V8 in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
Scope: local
bookworm: resolved (fixed in 75.0.3770.80-1)
bullseye: resolved (fixed in 75.0.3770.80-1)
forky: resolved (fixed in 75.0.3770.80-1)
sid: resolved (fixed in 75.0.3770.80-1)
trixie: resolved (fixed in 75.0.3770.80-1)
GHSA
GHSA-fwjh-4hpr-6hgj: Object lifecycle issue in V8 in Google Chrome prior to 75
ghsa_unreviewed·2022-05-24
CVE-2019-5831 [HIGH] CWE-787 GHSA-fwjh-4hpr-6hgj: Object lifecycle issue in V8 in Google Chrome prior to 75
Object lifecycle issue in V8 in Google Chrome prior to 75.0.3770.80 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
OSV
CVE-2019-5831: Object lifecycle issue in V8 in Google Chrome prior to 75
osv·2019-06-27·CVSS 8.8
CVE-2019-5831 [HIGH] CVE-2019-5831: Object lifecycle issue in V8 in Google Chrome prior to 75
Object lifecycle issue in V8 in Google Chrome prior to 75.0.3770.80 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-5831 chromium-browser: Incorrect map processing in V8
bugzilla·2019-06-07·CVSS 8.8
CVE-2019-5831 [HIGH] CVE-2019-5831 chromium-browser: Incorrect map processing in V8
CVE-2019-5831 chromium-browser: Incorrect map processing in V8
An incorrect map processing flaw was found in the V8 component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=950328
External References:
https://chromereleases.googleblog.com/2019/06/stable-channel-update-for-desktop.html
Discussion:
Created chromium tracking bugs for this issue:
Affects: epel-7 [bug 1718272]
Affects: fedora-all [bug 1718271]
---
This issue has been addressed in the following products:
Red Hat Enterprise Linux 6 Supplementary
Via RHSA-2019:1477 https://access.redhat.com/errata/RHSA-2019:1477
Bugzilla
CVE-2019-5828 CVE-2019-5829 CVE-2019-5830 CVE-2019-5831 CVE-2019-5832 CVE-2019-5833 CVE-2019-5834 CVE-2019-5835 CVE-2019-5836 CVE-2019-5837 CVE-2019-5838 CVE-2019-5839 CVE-2019-5840 chromium: various
bugzilla·2019-06-07·CVSS 8.8
CVE-2019-5828 [HIGH] CVE-2019-5828 CVE-2019-5829 CVE-2019-5830 CVE-2019-5831 CVE-2019-5832 CVE-2019-5833 CVE-2019-5834 CVE-2019-5835 CVE-2019-5836 CVE-2019-5837 CVE-2019-5838 CVE-2019-5839 CVE-2019-5840 chromium: various
CVE-2019-5828 CVE-2019-5829 CVE-2019-5830 CVE-2019-5831 CVE-2019-5832 CVE-2019-5833 CVE-2019-5834 CVE-2019-5835 CVE-2019-5836 CVE-2019-5837 CVE-2019-5838 CVE-2019-5839 CVE-2019-5840 chromium: various flaws [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 ment
Bugzilla
CVE-2019-5828 CVE-2019-5829 CVE-2019-5830 CVE-2019-5831 CVE-2019-5832 CVE-2019-5833 CVE-2019-5834 CVE-2019-5835 CVE-2019-5836 CVE-2019-5837 CVE-2019-5838 CVE-2019-5839 CVE-2019-5840 chromium: various
bugzilla·2019-06-07·CVSS 8.8
CVE-2019-5828 [HIGH] CVE-2019-5828 CVE-2019-5829 CVE-2019-5830 CVE-2019-5831 CVE-2019-5832 CVE-2019-5833 CVE-2019-5834 CVE-2019-5835 CVE-2019-5836 CVE-2019-5837 CVE-2019-5838 CVE-2019-5839 CVE-2019-5840 chromium: various
CVE-2019-5828 CVE-2019-5829 CVE-2019-5830 CVE-2019-5831 CVE-2019-5832 CVE-2019-5833 CVE-2019-5834 CVE-2019-5835 CVE-2019-5836 CVE-2019-5837 CVE-2019-5838 CVE-2019-5839 CVE-2019-5840 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-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 a
Talos
Vulnerability Spotlight: Google V8 Array.prototype memory corruption vulnerability
blogs_talos·2019-07-01·CVSS 8.8
[HIGH] Vulnerability Spotlight: Google V8 Array.prototype memory corruption vulnerability
The V8 JavaScript engine in Google Chrome contains a memory corruption vulnerability that could allow an attacker to gain the ability to execute arbitrary code on the victim’s machine. V8 is the core JavaScript engine that runs in the Chrome browser. As part of Chrome and node.is, it is the most popular JavaScript engine currently available.
In accordance with our coordinated disclosure policy, Cisco Talos worked with Google to ensure that these issues are resolved and that an update is available for affected customers. Google initially fixed this vulnerability in March and merged it in April. However, the company just publicly disclosed it on June 26, per its vulnerability disclosure policies.
### Vulnerability details
Google V8 Array.prototype memory corruption vulnerability (TALOS-20
Talos
Vulnerability Spotlight: Google V8 Array.prototype memory corruption vulnerability
blogs_talos·2019-07-01·CVSS 8.8
[HIGH] Vulnerability Spotlight: Google V8 Array.prototype memory corruption vulnerability
## Vulnerability Spotlight: Google V8 Array.prototype memory corruption vulnerability
The V8 JavaScript engine in Google Chrome contains a memory corruption vulnerability that could allow an attacker to gain the ability to execute arbitrary code on the victim’s machine. V8 is the core JavaScript engine that runs in the Chrome browser. As part of Chrome and node.is, it is the most popular JavaScript engine currently available. In accordance with our coordinated disclosure policy, Cisco Talos worked with Google to ensure that these issues are resolved and that an update is available for affected customers. Google initially fixed this vulnerability in March and merged it in April. However, the company just publicly disclosed it on June 26, per its vulnerability disclosure policies .
## Vuln
http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00085.htmlhttps://chromereleases.googleblog.com/2019/06/stable-channel-update-for-desktop.htmlhttps://crbug.com/950328https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CPM7VPE27DUNJLXM4F5PAAEFFWOEND6X/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EI3DGFVT7CKJO6YVMP55R35HCDVEIC4Z/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FKN4GPMBQ3SDXWB4HL45II5CZ7P2E4AI/https://seclists.org/bugtraq/2019/Aug/19https://security.gentoo.org/glsa/201908-18https://www.debian.org/security/2019/dsa-4500https://www.talosintelligence.com/vulnerability_reports/TALOS-2019-0791http://lists.opensuse.org/opensuse-security-announce/2019-06/msg00085.htmlhttps://chromereleases.googleblog.com/2019/06/stable-channel-update-for-desktop.htmlhttps://crbug.com/950328https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/CPM7VPE27DUNJLXM4F5PAAEFFWOEND6X/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/EI3DGFVT7CKJO6YVMP55R35HCDVEIC4Z/https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/FKN4GPMBQ3SDXWB4HL45II5CZ7P2E4AI/https://seclists.org/bugtraq/2019/Aug/19https://security.gentoo.org/glsa/201908-18https://www.debian.org/security/2019/dsa-4500https://www.talosintelligence.com/vulnerability_reports/TALOS-2019-0791
2019-06-27
Published