dbcve.org
ChromeWeb browser · Google

CVE-2019-5764

HIGH · 8.8 CVSS v3.0 Published 2019-02-19
Fix available
A fix is available. Upgrade to 72.0.3626.81 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
Incorrect pointer management in WebRTC in Google Chrome prior to 72.0.3626.81 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 pointer management vulnerability in WebRTC (the real-time communication component) in Google Chrome allows heap corruption through incorrect pointer handling. A remote attacker can exploit this by tricking users into visiting a crafted HTML page, potentially leading to arbitrary code execution.

MitigationUpdate Google Chrome to version 72.0.3626.81 or later to obtain the patched WebRTC component.

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:< 72.0.3626.81
Debian LinuxOperating system
Affected:= 9.0
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 6.0
Enterprise Linux WorkstationOperating system
Affected:= 6.0
FedoraOperating system
Affected:= 29= 30

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.0/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 if Google Chrome is installed
    Run `google-chrome --version` or `google-chrome-stable --version` on Linux. On Windows, check for Chrome in Program Files or via Add/Remove Programs.
    Affected if No Chrome installation means not affected by this specific Chrome vulnerability.
  2. Determine the installed Chrome version
    Execute `google-chrome --version` and note the full version number string returned.
    Affected if The command returns a version lower than 72.0.3626.81.
  3. Verify WebRTC component presence
    Open chrome://components in the Chrome address bar and look for the WebRTC version or presence entry. WebRTC is typically included in standard Chrome installations.
    Affected if WebRTC is present and the Chrome version is below 72.0.3626.81.
  4. Check Linux distribution package version (for Debian/RHEL/Fedora)
    On Debian: `dpkg -l | grep google-chrome`. On RHEL/Fedora: `rpm -qa | grep google-chrome`.
    Affected if The installed package version corresponds to Chrome versions below 72.0.3626.81.

A user is affected if Google Chrome is installed with a version lower than 72.0.3626.81 and the WebRTC component is present.

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 72.0.3626.81 or later
Fixed in 72.0.3626.81
Interim mitigation

Update Google Chrome to version 72.0.3626.81 or later to obtain the patched WebRTC component.

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5764 — 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-5764 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