CVE-2019-13735
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 write in JavaScript in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to execute arbitrary code inside a sandbox 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 confidenceOut-of-bounds write vulnerability in Google Chrome's JavaScript engine (V8) prior to version 79.0.3945.79. A remote attacker can exploit this via a crafted HTML page to execute arbitrary code. While the vulnerability allows code execution, it is constrained by Chrome's sandbox, reducing but not eliminating the risk.
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< 79.0.3945.79= 9.0= 10.0= 30= 31= 6.0= 6.0= 6.0= 6.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 Google Chrome browser versionOpen Chrome, click the three-dot menu, select Help > About Google Chrome. The version number is displayed on that page. Alternatively, navigate to chrome://settings/help in the address bar.Affected if The displayed version is earlier than 79.0.3945.79 (for example, 78.0.3904.108, 78.5.0, etc.)
-
Check Chrome version on Debian LinuxRun command: dpkg -l | grep google-chrome or apt-cache policy google-chrome-stableAffected if The installed version shown is earlier than 79.0.3945.79, or the package is not installed but the system is Debian 9.0 or 10.0 with Chrome added from third-party repositories
-
Check Chrome version on FedoraRun command: rpm -qa | grep google-chrome or dnf list installed google-chrome-stableAffected if The installed version shown is earlier than 79.0.3945.79, or the system is Fedora 30 or 31 with Chrome installed from third-party repos
-
Check Chrome version on RHEL-based systemsRun command: rpm -qa | grep google-chrome or yum list installed google-chrome-stableAffected if The installed version shown is earlier than 79.0.3945.79, or the system is RHEL 6.0 (Desktop, Server, Workstation, or Scientific Computing) with Chrome installed
You are affected if Google Chrome (or a Chrome-based browser) is installed with a version number lower than 79.0.3945.79, or if you are running any of the listed Debian, Fedora, or RHEL versions with Chrome added from third-party repositories.
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 data79.0.3945.79
Update Google Chrome to version 79.0.3945.79 or later to patch the vulnerability. In enterprise environments, deploy the update via endpoint management tools and verify completion across managed endpoints.
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13735 — 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-13735 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