ChromeWeb browser · Google
CVE-2019-13725
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 · uneditedUse-after-free in Bluetooth in Google Chrome prior to 79.0.3945.79 allowed a remote attacker to execute arbitrary code 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 confidenceUse-after-free vulnerability in Google Chrome's Bluetooth implementation allows a remote attacker to execute arbitrary code via a crafted HTML page. The flaw occurs when memory is accessed after being freed, enabling potential code execution in the browser context.
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
< 79.0.3945.79
Debian LinuxOperating system
= 9.0= 10.0
FedoraOperating system
= 30= 31
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux For Scientific ComputingOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 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.
-
Confirm Google Chrome is installedCheck for Chrome binary location: on Linux typically /usr/bin/google-chrome or /opt/google/chrome/google-chrome; on Windows check Program Files for Google Chrome folderAffected if Google Chrome browser is present on the system
-
Determine installed Chrome versionRun 'google-chrome --version' on Linux or check Chrome menu > Help > About Google Chrome on Windows/MacAffected if Version number returned is lower than 79.0.3945.79
-
Verify Bluetooth usage or configurationInspect if Bluetooth API is accessible in Chrome: open chrome://bluetooth-internals/ in Chrome browser, or check system Bluetooth service statusAffected if Bluetooth is enabled and the browser has access to Bluetooth APIs, making the attack surface active
-
Check distribution-specific package version (Linux)On Debian: dpkg -l | grep google-chrome; On Fedora: rpm -qa | grep chrome; On RHEL: rpm -qa | grep -i chromeAffected if Installed package version is below 79.0.3945.79 or matches vulnerable distribution versions (Debian 9/10, Fedora 30/31, RHEL 6.0)
User is affected if Google Chrome (or Chromium-based browser) version is below 79.0.3945.79 and the browser has Bluetooth functionality enabled or accessible.
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. Organizations should deploy the browser update through their standard patch management processes.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13725 — 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-13725 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