dbcve.org
ChromeWeb browser · Google

CVE-2023-1529

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-21
Fix available
A fix is available. Upgrade to 111.0.5563.110 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Out of bounds memory access in WebHID in Google Chrome prior to 111.0.5563.110 allowed a remote attacker to potentially exploit heap corruption via a malicious HID device. (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

An out-of-bounds memory access vulnerability in Google Chrome's WebHID (Web Human Interface Device) API allows a remote attacker to potentially exploit heap corruption by using a malicious HID device. The vulnerability exists in versions prior to 111.0.5563.110.

MitigationUpdate Google Chrome to version 111.0.5563.110 or later to remediate this vulnerability. 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:< 111.0.5563.110
FedoraOperating system
Affected:= 36= 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Determine the installed Google Chrome version
    Open chrome://version in the browser address bar, or run 'google-chrome --version' from command line, or right-click the Chrome shortcut and select 'Properties' to view file version
    Affected if The displayed version is lower than 111.0.5563.110 (e.g., 111.0.5563.64 or earlier)
  2. Check if Chrome is running as a system package on Fedora
    On Fedora systems, run 'rpm -qa | grep -i chrome' or 'dnf list installed | grep -i chrome' to list installed Chrome/Chromium packages
    Affected if The system has google-chrome-stable or chromium packages installed with versions below 111.0.5563.110 (check using 'rpm -q --qf "%{VERSION}-%{RELEASE}" <packagename>')
  3. Identify the Chromium open-source base version (if using non-Google Chrome browsers)
    Run 'chromium --version' or check the browser's about screen to determine the underlying Chromium version number
    Affected if The Chromium version is earlier than 111.0.5563.110 regardless of the browser branding
  4. Verify the WebHID API is accessible in the browser environment
    Visit chrome://flags/#enable-webhid in Chrome to confirm the WebHID feature flag status; note that the API is enabled by default in affected versions
    Affected if The browser version is vulnerable (steps 1-3) and WebHID is not explicitly disabled via the flag or enterprise policy

Your environment is affected if you are running any Chrome or Chromium-based browser version prior to 111.0.5563.110 on Fedora 36/37/38, or on any operating system, with WebHID API functionality available (the default state).

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

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

Recommended fix High confidence

Chrome 111.0.5563.110 or later

  1. Upgrade Google Chrome to version 111.0.5563.110 or later
  2. On Fedora systems, run 'sudo dnf update google-chrome-stable' to apply the security update
  3. Restart the browser after updating to ensure the fix is applied
  4. Verify the version by navigating to chrome://settings/help to confirm the installed version is 111.0.5563.110 or higher

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-1529 — 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-1529 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