dbcve.org
ChromeWeb browser · Google

CVE-2023-1820

HIGH · 8.8 CVSS v3.1 Published 2023-04-04
Fix available
A fix is available. Upgrade to 112.0.5615.49 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Heap buffer overflow in Browser History in Google Chrome prior to 112.0.5615.49 allowed a remote attacker who convinced a user to engage in specific UI interaction 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 · high confidence

Heap buffer overflow vulnerability in Google Chrome's Browser History component allows remote attackers to corrupt heap memory via specially crafted HTML pages that trick users into specific UI interactions, potentially enabling arbitrary code execution.

MitigationUpdate Google Chrome to version 112.0.5615.49 or later to obtain the official patch. Organizations should deploy the update via patch management systems.

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
Affected:< 112.0.5615.49
FedoraOperating system
Affected:= 36= 37
Debian LinuxOperating system
Affected:= 11.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Google Chrome is installed
    On Windows, check Program Files/Google/Chrome/Application/chrome.exe version via Properties, or run 'chrome --version' from command line. On Linux, run 'google-chrome --version' or 'chromium --version'. On macOS, run '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version'
    Affected if Google Chrome browser is present on the system
  2. Determine installed Chrome version
    Execute 'google-chrome --version' in terminal or check chrome://help page within the browser
    Affected if Version number is lower than 112.0.5615.49 (e.g., 112.0.5615.48 or earlier)
  3. Confirm Browser History feature accessibility
    The vulnerability requires user interaction with the Browser History component - verify the History page is accessible via chrome://history or by pressing Ctrl+H
    Affected if History feature is enabled and accessible to the user account
  4. Check Linux OS version if applicable
    On Fedora systems, run 'cat /etc/fedora-release'. On Debian, run 'cat /etc/debian_version'
    Affected if Running Fedora 36 or 37, or Debian 11.0, with an unpatched Chrome version

You are affected if Google Chrome (or Chromium) is installed with a version below 112.0.5615.49 and the Browser History feature is accessible on the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 112.0.5615.49 or later
Fixed in 112.0.5615.49
Interim mitigation

Update Google Chrome to version 112.0.5615.49 or later to obtain the official patch. Organizations should deploy the update via patch management systems.

Recommended fix High confidence

Google Chrome 112.0.5615.49 or later

  1. Open Google Chrome and navigate to chrome://settings/help to check for updates
  2. Chrome will automatically check for and download version 112.0.5615.49 or later
  3. Click 'Update Google Chrome' if an update is available
  4. Restart the browser to apply the update
  5. Alternatively, download and install the latest stable Chrome from https://www.google.com/chrome

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-1820 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-1820 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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