ChromeWeb browser · Google
CVE-2019-5769
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 · uneditedIncorrect handling of invalid end character position when front rendering in Blink 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 confidenceHeap corruption vulnerability in Google Chrome's Blink rendering engine caused by incorrect handling of invalid end character position during front rendering. A remote attacker could exploit this via a crafted HTML page to potentially execute arbitrary code.
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
< 72.0.3626.81
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0
Debian LinuxOperating system
= 9.0
FedoraOperating system
= 29= 30CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Google Chrome is installedLook for chrome binary in common locations: /usr/bin/google-chrome, /usr/bin/chromium, /usr/bin/chromium-browser, or check via package manager (dpkg -l | grep -i chrome, rpm -qa | grep -i chrome)Affected if No Chrome/Chromium browser is found on the system - the user is not affected by this CVE.
-
Determine installed Chrome versionRun 'google-chrome --version' or 'chromium --version' or 'chromium-browser --version' from the command line. Alternatively, open Chrome and navigate to chrome://version to see the full version string.Affected if Unable to determine version - cannot assess vulnerability status.
-
Compare version against vulnerable rangeParse the version number from step 2 and compare it to the affected version: versions prior to 72.0.3626.81 are vulnerable. For example, 72.0.3626.80 and below are affected; 72.0.3626.81 and above are patched.Affected if Installed version is less than 72.0.3626.81 - the browser is vulnerable to this CVE.
-
Verify browser is actually usableConfirm the Chrome/Chromium browser can be launched and renders web pages. This is a Blink rendering engine flaw, so the browser must be functional for the vulnerability to be relevant.Affected if Browser is installed but cannot launch or render content - the exploitation vector is not accessible.
A user is affected if Google Chrome or Chromium is installed with a version number lower than 72.0.3626.81 and the browser is functional enough to render web content.
Generated from the published advisory. Verify against your own configuration.
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 data72.0.3626.81
Upgrade Google Chrome to version 72.0.3626.81 or later to patch the vulnerability.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2019-5769 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-5769 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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