ChromeWeb browser · Google
CVE-2023-3079
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 · uneditedType confusion in V8 in Google Chrome prior to 114.0.5735.110 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 confidenceType confusion vulnerability in Google Chrome's V8 JavaScript engine allows a remote attacker to potentially exploit heap corruption via a crafted malicious HTML page, potentially leading to arbitrary 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
< 114.0.5735.110
FedoraOperating system
= 37= 38
Debian LinuxOperating system
= 11.0= 12.0
Linux KernelOperating system
all versionsall versions< 7.1.5= 7.2.0CVSS 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 versionOpen chrome://version in Chrome browser or go to Menu > Help > About Google ChromeAffected if The displayed version is earlier than 114.0.5735.110
-
Identify Chromium-based browsersList installed browsers (common ones include Edge, Brave, Opera) and check their version via browser menu or about pagesAffected if The browser is Chromium-based and its version corresponds to a Chrome version earlier than 114.0.5735.110
-
Check Couchbase Server versionRun 'couchbase-cli server-info' or check the Couchbase UI/admin consoleAffected if The installed version is below 7.1.5 or exactly 7.2.0
You are affected if you run Google Chrome or a Chromium-based browser before version 114.0.5735.110, or Couchbase Server versions below 7.1.5 or exactly 7.2.0.
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 · scoped7.1.5114.0.5735.110
Update Google Chrome to version 114.0.5735.110 or later to patch the V8 type confusion vulnerability.
Chrome 114.0.5735.110 or later; Couchbase Server 7.1.5+ or 7.2.1+
- 1. Identify the installed Chrome/Chromium version by navigating to chrome://settings/help or running 'google-chrome --version' / 'chromium --version'
- 2. If the version is earlier than 114.0.5735.110, download the latest stable Chrome release from google.com/chrome or your system's package manager
- 3. For Fedora: Run 'sudo dnf update chromium' or 'sudo dnf update google-chrome'
- 4. For Debian/Ubuntu: Run 'sudo apt update && sudo apt upgrade chromium' or 'sudo apt upgrade google-chrome-stable'
- 5. For macOS: Download and install Chrome from google.com/chrome, or run 'brew upgrade google-chrome'
- 6. Restart the browser after update
- 7. For Couchbase Server: Upgrade to version 7.1.5 or later, or 7.2.1 or later if available
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3079 — 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-3079 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