dbcve.org
ChromeWeb browser · Google

CVE-2023-4572

HIGH · 8.8 CVSS v3.1 Published 2023-08-29
Fix available
A fix is available. Upgrade to 116.0.5845.140 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 MediaStream in Google Chrome prior to 116.0.5845.140 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

Use after free vulnerability in Chrome's MediaStream component allows a remote attacker to exploit heap corruption via a crafted HTML page, potentially achieving code execution.

MitigationUpdate Google Chrome to version 116.0.5845.140 or later to patch the vulnerability.

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:< 116.0.5845.140
FedoraOperating system
Affected:= 37= 38= 39
Debian LinuxOperating system
Affected:= 11.0= 12.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 installed Chrome browser
    Check if Google Chrome or Chromium is installed on the system. On Linux, use package manager commands like 'rpm -q google-chrome' or 'dpkg -l | grep -i chromium'. On Windows, check Program Files for Chrome installation.
    Affected if Google Chrome or Chromium browser is present on the system
  2. Determine Chrome version number
    Open Chrome and navigate to chrome://version, or run 'google-chrome --version' in terminal. For Chromium, try 'chromium --version' or check the package version via the system package manager.
    Affected if The installed version is lower than 116.0.5845.140
  3. Verify affected operating systems
    Confirm the operating system version. For Fedora, run 'cat /etc/fedora-release'. For Debian, run 'cat /etc/debian_version'.
    Affected if Running Fedora 37, 38, or 39, or Debian 11.0 or 12.0 with an affected Chrome version
  4. Confirm MediaStream usage context
    The vulnerability is triggered by loading a crafted HTML page that utilizes the MediaStream API. There is no specific configuration flag to check; the flaw exists in the MediaStream component code itself when processing certain media operations.
    Affected if The vulnerability is triggerable through any webpage using MediaStream functionality when combined with an affected Chrome version

A user is affected if they have Google Chrome or Chromium installed with a version lower than 116.0.5845.140 on Fedora 37/38/39 or Debian 11.0/12.0.

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

Update Google Chrome to version 116.0.5845.140 or later to patch the vulnerability.

Recommended fix High confidence

Chrome 116.0.5845.140 or later

  1. Update Google Chrome to version 116.0.5845.140 or later by visiting chrome://settings/help and clicking 'Update Google Chrome'
  2. For Fedora systems, run: sudo dnf update google-chrome-stable
  3. For Debian systems, update via: sudo apt update && sudo apt upgrade chromium (or google-chrome-stable)
  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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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