dbcve.org
ChromeWeb browser · Google

CVE-2023-2134

HIGH · 8.8 CVSS v3.1 Published 2023-04-19
Fix available
A fix is available. Upgrade to 112.0.5615.137 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
Out of bounds memory access in Service Worker API 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: 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 confidence

Out-of-bounds memory access vulnerability in Google Chrome's Service Worker API prior to version 112.0.5615.137. A remote attacker can exploit this via a crafted HTML page to potentially corrupt heap memory, leading to arbitrary code execution.

MitigationUpdate Google Chrome to version 112.0.5615.137 or later. Apply the update through your organization's endpoint management/ patch management solution to ensure all affected systems receive the patch.

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

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. Check Chrome version via command line
    Open a terminal and run: google-chrome --version or chromium --version or chrome --version depending on the installed browser binary name
    Affected if The returned version number is lower than 112.0.5615.137
  2. Check Chrome version from browser UI
    Open Google Chrome, navigate to chrome://version in the address bar, and note the version listed under 'Google Chrome'
    Affected if The displayed version is below 112.0.5615.137
  3. Verify Service Worker API usage
    This vulnerability requires the Service Worker API to be enabled and accessible to a crafted webpage. Check if your browser has Service Workers enabled by visiting chrome://inspect/#service-workers
    Affected if Service Workers are enabled and the browser version is vulnerable (below 112.0.5615.137)
  4. Check Linux distribution package version (Debian/Fedora)
    On Debian run: dpkg -l | grep chromium or apt show chromium. On Fedora run: rpm -qa | grep chromium or dnf list installed chromium
    Affected if The installed package version corresponds to a Chromium build lower than 112.0.5615.137

You are affected if Google Chrome or Chromium is installed with a version number below 112.0.5615.137 and Service Worker API functionality is available in the browser.

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.137 or later
Fixed in 112.0.5615.137
Interim mitigation

Update Google Chrome to version 112.0.5615.137 or later. Apply the update through your organization's endpoint management/ patch management solution to ensure all affected systems receive the patch.

Recommended fix High confidence

Chrome 112.0.5615.137 or later

  1. Check current Chrome version by navigating to chrome://version or Help > About Google Chrome
  2. For Chrome on any platform: Download and install Chrome 112.0.5615.137 or later from google.com/chrome
  3. For Debian Linux (11.0): Run 'sudo apt-get update && sudo apt-get upgrade' to update the chromium package
  4. For Fedora (36, 37, 38): Run 'sudo dnf update' to update the chromium package
  5. Restart Chrome after the update to apply the fix

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-2134 — 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-2134 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