ChromeWeb browser · Google
CVE-2019-13700
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 · uneditedOut of bounds memory access in the gamepad API in Google Chrome prior to 78.0.3904.70 allowed a remote attacker who had compromised the renderer process 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 confidenceAn out-of-bounds memory access vulnerability existed in the Gamepad API of Google Chrome prior to version 78.0.3904.70. A remote attacker who had already compromised the renderer process could exploit this vulnerability by serving a crafted HTML page, potentially causing heap corruption.
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
< 78.0.3904.70= 15.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Google Chrome is installedOn Linux: check for /usr/bin/google-chrome or /opt/google/chrome/google-chrome. On Windows: check C:\Program Files\Google\Chrome\Application\chrome.exe. On macOS: check /Applications/Google Chrome.appAffected if Google Chrome is not found on the system, the vulnerability does not apply
-
Determine installed Chrome versionRun 'google-chrome --version' on Linux, or right-click Chrome shortcut and select Properties > Details on Windows, or run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' on macOSAffected if The version number returned is lower than 78.0.3904.70 (e.g., 77.x.x.x or earlier)
-
Verify Chrome package source on OpenSUSEOn OpenSUSE: run 'rpm -qi google-chrome-stable' or check /etc/zypp/repos.d/ for Chrome repositories. Run 'zypper se -i google-chrome'Affected if Chrome was installed from OpenSUSE Backports SLE 15.0 repository and version is below 78.0.3904.70
-
Confirm renderer process exposureThis vulnerability requires a compromised renderer process. Check if Chrome is running with sandbox disabled (--no-sandbox flag) or if the user has granted unusual extensions/permissionsAffected if Chrome is running with sandbox disabled or with untrusted extensions that could compromise the renderer process
A user is affected if they have Google Chrome installed with a version lower than 78.0.3904.70, especially if running with sandbox disabled or untrusted extensions that could provide renderer compromise.
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 data78.0.3904.70
Update Google Chrome to version 78.0.3904.70 or later to patch this vulnerability.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13700 — 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-13700 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