ChromeWeb browser · Google
CVE-2023-5187
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 Extensions in Google Chrome prior to 117.0.5938.132 allowed an attacker who convinced a user to install a malicious extension to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)
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 Extensions component prior to version 117.0.5938.132. An attacker can exploit heap corruption by tricking a user into installing a malicious extension that triggers the vulnerability through a crafted HTML page.
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
< 117.0.5938.132
Debian LinuxOperating system
= 11.0= 12.0
FedoraOperating system
= 37= 38= 39CVSS 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 installed Chrome versionNavigate to chrome://version in the Chrome browser or run 'google-chrome --version' in terminalAffected if Version number is less than 117.0.5938.132
-
Verify Chrome package version on DebianRun 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable'Affected if Installed package version is earlier than 117.0.5938.132-1
-
Verify Chrome package version on FedoraRun 'rpm -qa | grep google-chrome' or 'dnf info google-chrome-stable'Affected if Installed package version is earlier than 117.0.5938.132-1
-
Confirm Extensions feature is in useCheck if any extensions are installed by navigating to chrome://extensionsAffected if Any extensions are installed and the Chrome version is below 117.0.5938.132
A user is affected if their Google Chrome version is below 117.0.5938.132 and they have any extensions installed, as the vulnerability resides in the Extensions component.
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.
dbcve · scoped117.0.5938.132
Update Google Chrome to version 117.0.5938.132 or later. Organizations should enforce browser update policies and restrict extension installation to trusted sources.
Chrome 117.0.5938.132 or later
- Open Google Chrome browser
- Navigate to Help > About Google Chrome
- Click 'Check for updates' or wait for automatic update check
- If version 117.0.5938.132 or later is available, let it download and install
- Restart Chrome browser to complete the update
- Alternatively, for Linux systems, run: sudo apt update && sudo apt upgrade google-chrome-stable (Debian) or sudo dnf update chrome (Fedora)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5187 — 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-2023-5187 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