dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 8 May 2023.
ChromeWeb browser · Google

CVE-2023-2033

HIGH · 8.8 CVSS v3.1 Published 2023-04-14
Fix available
A fix is available. Upgrade to 7.1.5 / 112.0.5615.121 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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
Type confusion in V8 in Google Chrome prior to 112.0.5615.121 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

A type confusion vulnerability exists in the V8 JavaScript engine in Google Chrome versions prior to 112.0.5615.121. An attacker can exploit this by tricking users into visiting a crafted HTML page, potentially leading to heap corruption and arbitrary code execution.

MitigationUpdate Google Chrome to version 112.0.5615.121 or later. Organizations should deploy browser updates through their 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.121
Debian LinuxOperating system
Affected:= 11.0
FedoraOperating system
Affected:= 36= 37= 38
Couchbase ServerApplication
Affected:< 7.1.5= 7.2.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. Check Google Chrome version
    Open chrome://version in Chrome browser or go to Help > About Google Chrome
    Affected if Version displayed is less than 112.0.5615.121
  2. Check Chromium browser version on Debian 11
    Run command: dpkg -l | grep chromium or apt show chromium
    Affected if Chromium package version is installed and less than the fixed version in Debian 11 repositories
  3. Check Chromium browser version on Fedora
    Run command: rpm -qa | grep chromium or dnf info chromium
    Affected if Chromium version is installed from Fedora 36, 37, or 38 repositories and is less than the patched version
  4. Check Node.js V8 engine version
    Run command: node -e "console.log(process.versions.v8)" to see V8 engine version embedded in Node.js
    Affected if Node.js is installed and uses a V8 version that matches the vulnerable Chrome version range
  5. Check Couchbase Server version
    Run command: cbas-cli -version or check via Couchbase Admin UI under Settings > About, or query: SELECT version()
    Affected if Couchbase Server version is less than 7.1.5 or exactly equals 7.2.0

User is affected if Google Chrome, Chromium browser on Debian/Fedora, or Couchbase Server is running a version within the specified vulnerable ranges and the V8 JavaScript engine is processing untrusted JavaScript code.

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 7.1.5 / 112.0.5615.121 or later
Fixed in 7.1.5112.0.5615.121
Interim mitigation

Update Google Chrome to version 112.0.5615.121 or later. Organizations should deploy browser updates through their patch management systems.

Recommended fix Moderate confidence

Chrome/Chromium: 112.0.5615.121 or later | Couchbase Server: 7.1.5+ or patched 7.2.x

  1. For Chrome/Chromium-based browsers: Upgrade to Chrome version 112.0.5615.121 or later
  2. For Chrome on Linux distributions (Debian 11, Fedora 36-38): Update the chromium or google-chrome package via system package manager (e.g., 'dnf update chromium' or 'apt update && apt upgrade chromium')
  3. For Couchbase Server: Upgrade to version 7.1.5 or later, or upgrade from 7.2.0 to a patched 7.2.x release

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

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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