dbcve.org
ChromeWeb browser · Google

CVE-2023-5218

HIGH · 8.8 CVSS v3.1 Published 2023-10-11
Fix available
A fix is available. Upgrade to 118.0.5993.70 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
Use after free in Site Isolation in Google Chrome prior to 118.0.5993.70 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Critical)

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 use-after-free vulnerability exists in Google Chrome's Site Isolation feature prior to version 118.0.5993.70. Site Isolation is a security mechanism that isolates websites into separate processes to prevent cross-origin attacks. The vulnerability allows a remote attacker to exploit heap corruption through a specially crafted HTML page, potentially leading to arbitrary code execution.

MitigationUpdate Google Chrome to version 118.0.5993.70 or later. Deploy the update through enterprise patch management systems and verify completion across affected endpoints.

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:< 118.0.5993.70
Debian LinuxOperating system
Affected:= 11.0= 12.0
FedoraOperating system
Affected:= 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 Google Chrome version
    Navigate to chrome://settings/help or use 'google-chrome --version' in terminal to see installed version
    Affected if Version is lower than 118.0.5993.70
  2. Check if Site Isolation is enabled
    Navigate to chrome://flags/#enable-site-per-process in Chrome - if the flag shows as 'Enabled' or not 'Disabled', Site Isolation is active
    Affected if Site Isolation feature is enabled (this is required for the vulnerability to be exploitable)
  3. Check Debian package version (Debian 11/12)
    Run 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable' in terminal
    Affected if Package version shown is lower than 118.0.5993.70 or the package is not installed at all but Chrome browser exists from another source
  4. Check Fedora package version (Fedora 37/38)
    Run 'rpm -qa | grep google-chrome' or 'dnf info google-chrome-stable' in terminal
    Affected if Package version shown is lower than 118.0.5993.70 or Chrome is installed via rpm but version is not at or above the fix

User is affected if they are running any Google Chrome version below 118.0.5993.70 AND have Site Isolation enabled or are using the default Chrome configuration where Site Isolation may be active for certain site types.

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 118.0.5993.70 or later
Fixed in 118.0.5993.70
Interim mitigation

Update Google Chrome to version 118.0.5993.70 or later. Deploy the update through enterprise patch management systems and verify completion across affected endpoints.

Recommended fix High confidence

Chrome 118.0.5993.70 or later

  1. Update Google Chrome to version 118.0.5993.70 or later by visiting chrome://settings/help or using the built-in update mechanism
  2. For Debian Linux users: Run 'apt-get update && apt-get upgrade' or 'apt-get update && apt-get install chromium' to get the updated package
  3. For Fedora users: Run 'dnf update chromium' to get the updated package
  4. Restart the browser after updating

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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