dbcve.org
ChromeWeb browser · Google

CVE-2019-5831

HIGH · 8.8 CVSS v3.1 Published 2019-06-27
Fix available
A fix is available. Upgrade to 75.0.3770.80 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A lifecycle management flaw in Google Chrome's V8 JavaScript engine allowed improper handling of objects during their lifecycle, enabling heap corruption when processing a specially crafted HTML page. This could permit a remote attacker to execute arbitrary code.

MitigationUpgrade Google Chrome to version 75.0.3770.80 or later to address the V8 object lifecycle vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:< 75.0.3770.80
Debian LinuxOperating system
Affected:= 10.0
FedoraOperating system
Affected:= 29= 30
BackportsOperating system
Affected:= sle-15
LeapOperating system
Affected:= 15.0= 15.1= 42.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Google Chrome version
    Open Chrome, click the menu (three dots) > Help > About Google Chrome, or navigate to chrome://settings/help
    Affected if Version displayed is lower than 75.0.3770.80
  2. Check Chrome version via command line (Windows)
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome" /v Version' in Command Prompt or PowerShell
    Affected if Returned version number is less than 75.0.3770.80
  3. Check Chrome version via command line (macOS)
    Run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' in Terminal
    Affected if Returned version number is less than 75.0.3770.80
  4. Check installed Chrome package on Linux (Debian/Ubuntu)
    Run 'dpkg -l | grep google-chrome' or 'apt show google-chrome-stable'
    Affected if Installed version is lower than 75.0.3770.80-1 or version not shown
  5. Check Chrome on Fedora/RHEL systems
    Run 'rpm -qa | grep chrome' or 'dnf list installed | grep chrome'
    Affected if Installed version is lower than 75.0.3770.80
  6. Check Chrome on openSUSE systems
    Run 'rpm -qa | grep chrome' or 'zypper se google-chrome'
    Affected if Installed version is lower than 75.0.3770.80

If Google Chrome version is less than 75.0.3770.80, the system is affected by this V8 lifecycle vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 75.0.3770.80 or later
Fixed in 75.0.3770.80
Interim mitigation

Upgrade Google Chrome to version 75.0.3770.80 or later to address the V8 object lifecycle vulnerability.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5831 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-5831 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data