dbcve.org
ChromeWeb browser · Google

CVE-2023-2461

HIGH · 8.8 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to 113.0.5672.63 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 OS Inputs in Google Chrome on ChromeOS prior to 113.0.5672.63 allowed a remote attacker who convinced a user to enage in specific UI interaction to potentially exploit heap corruption via crafted UI interaction. (Chromium security severity: Medium)

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 OS Inputs component of Google Chrome on ChromeOS versions prior to 113.0.5672.63. A remote attacker can exploit this through specific UI interactions to potentially achieve heap corruption, allowing potential code execution or data corruption.

MitigationUpdate Google Chrome on ChromeOS to version 113.0.5672.63 or later to patch the vulnerability. In enterprise environments, deploy the update via Chrome Enterprise policies.

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:< 113.0.5672.63
Debian LinuxOperating system
Affected:= 11.0
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
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 Chrome version on ChromeOS
    Navigate to chrome://version in the Chrome browser or run 'google-chrome --version' in the ChromeOS terminal
    Affected if Version is earlier than 113.0.5672.63
  2. Check Chrome version on Debian Linux
    Run 'google-chrome --version' or 'chromium --version' in the terminal
    Affected if Running Debian 11 and Chrome version is earlier than 113.0.5672.63
  3. Check Chrome version on Fedora Linux
    Run 'google-chrome --version' or 'chromium --version' in the terminal
    Affected if Running Fedora 36, 37, or 38 and Chrome version is earlier than 113.0.5672.63
  4. Confirm vulnerability trigger condition
    This flaw requires specific UI interactions with the OS Inputs component - ensure users are not engaging with untrusted input interfaces
    Affected if Users can interact with the OS Inputs component through untrusted UI elements

You are affected if Google Chrome (on ChromeOS, Debian 11, or Fedora 36-38) is installed with a version number lower than 113.0.5672.63 and users can interact with the OS Inputs component through specific UI interactions.

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

Update Google Chrome on ChromeOS to version 113.0.5672.63 or later to patch the vulnerability. In enterprise environments, deploy the update via Chrome Enterprise policies.

Recommended fix High confidence

Chrome/Chromium 113.0.5672.63 or later

  1. Check current Chrome/Chromium version by navigating to chrome://settings/help or running 'chromium --version'
  2. Update Chrome to version 113.0.5672.63 or later by navigating to Chrome menu > Help > About Google Chrome and clicking 'Update Google Chrome'
  3. For Linux distributions (Debian 11, Fedora 36-38), update the system package: run 'sudo apt-get update && sudo apt-get upgrade' (Debian) or 'sudo dnf update' (Fedata) to receive the patched Chromium package
  4. Restart the browser after the update completes
  5. Verify the version is now 113.0.5672.63 or later

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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