dbcve.org
ChromeWeb browser · Google

CVE-2023-5482

HIGH · 8.8 CVSS v3.1 Published 2023-11-01
Fix available
A fix is available. Upgrade to 119.0.6045.105 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
Insufficient data validation in USB in Google Chrome prior to 119.0.6045.105 allowed a remote attacker to perform out of bounds memory access 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

Insufficient data validation in Google Chrome's USB handling prior to version 119.0.6045.105 allows a remote attacker to achieve out-of-bounds memory access via a maliciously crafted HTML page, potentially leading to memory corruption or information disclosure.

MitigationUpdate Google Chrome to version 119.0.6045.105 or later. Organizations should deploy the browser update through their standard patch management processes.

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:< 119.0.6045.105
Debian LinuxOperating system
Affected:= 11.0= 12.0
FedoraOperating system
Affected:= 37= 38= 39

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 installed Google Chrome version
    Open Chrome, navigate to Settings > About Chrome, or visit chrome://settings/help. Alternatively, run 'google-chrome --version' or 'chrome --version' in terminal.
    Affected if Version number is less than 119.0.6045.105 (e.g., 119.0.6045.104, 118.x.x.x, etc.)
  2. Identify Chrome package source on Linux
    On Debian-based systems, run 'dpkg -l | grep google-chrome' or check /opt/google/chrome/. On Fedora/RHEL, run 'rpm -qa | grep chrome' or check /usr/bin/google-chrome.
    Affected if Google Chrome browser is installed from any source and version check returns a version below 119.0.6045.105
  3. Verify Chromium browser variant
    Run 'chromium --version' or 'chromium-browser --version' in terminal. Check /usr/bin/chromium or /usr/bin/chromium-browser.
    Affected if Chromium-based browser is installed and its version corresponds to the Chrome release tree prior to 119.0.6045.105

A user is affected if Google Chrome or a Chromium-based browser with the same vulnerable USB handling code is installed with a version lower than 119.0.6045.105.

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

Update Google Chrome to version 119.0.6045.105 or later. Organizations should deploy the browser update through their standard patch management processes.

Recommended fix High confidence

Chrome/Chromium 119.0.6045.105 or later

  1. Check current Chrome/Chromium version by navigating to chrome://settings/help or chromium --version in terminal
  2. Update Chrome to version 119.0.6045.105 or later: On Linux distributions (Debian 11/12, Fedora 37/38/39), run 'sudo apt update && sudo apt upgrade' or 'sudo dnf update' respectively to apply security updates for chromium-browser packages
  3. Alternatively, download the latest stable Chrome from official sources: https://www.google.com/chrome/
  4. Restart the browser after updating to ensure the fix is applied
  5. Verify the version after update confirms 119.0.6045.105 or later is installed
Caveat No significant breaking changes expected; Chrome auto-updates typically include security fixes without disrupting user experience

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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