ChromeWeb browser · Google
CVE-2023-2137
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 · uneditedHeap buffer overflow in sqlite in Google Chrome prior to 112.0.5615.137 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)
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 · moderate confidenceHeap buffer overflow vulnerability in the SQLite library embedded in Google Chrome. A remote attacker can exploit this by luring a user to visit a crafted HTML page that triggers the overflow in SQLite's memory handling, potentially leading to heap corruption and possible remote code execution.
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
< 112.0.5615.137
Debian LinuxOperating system
= 11.0
FedoraOperating system
= 36= 37= 38CVSS 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 version on Windows/macOS/LinuxNavigate to chrome://settings/help or use 'google-chrome --version' in terminalAffected if Version is earlier than 112.0.5615.137
-
Check installed Chrome package on Debian LinuxRun 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable'Affected if Package is installed and version is earlier than 112.0.5615.137-1
-
Check installed Chrome package on FedoraRun 'rpm -qa | grep google-chrome' or 'dnf info google-chrome-stable'Affected if Package is installed and version is earlier than 112.0.5615.137-1
-
Verify Chrome is actively usedCheck if Google Chrome is the primary or configured browser in your environmentAffected if Chrome is installed and in active use, meeting the version conditions above
You are affected if Google Chrome (any variant: stable, beta, or from distro packages) is installed with a version number lower than 112.0.5615.137, since the embedded SQLite library contains the heap buffer overflow that can be triggered by visiting crafted HTML pages.
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 · scoped112.0.5615.137
Upgrade Google Chrome to version 112.0.5615.137 or later. In enterprise environments, deploy the updated browser version organization-wide through standard patch management processes.
Chrome 112.0.5615.137 or later
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Alternatively, navigate to chrome://settings/help
- Click 'Check for updates' or wait for automatic update check
- Ensure Chrome updates to version 112.0.5615.137 or later
- Restart the browser after update completes
- For Linux distributions (Debian 11, Fedora 36-38): Run 'sudo apt update && sudo apt upgrade' (Debian) or 'sudo dnf update' (Fedana) to update the Chrome package
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
- 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-2023-2137 — 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-2137 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