dbcve.org
ChromeWeb browser · Google

CVE-2023-2722

HIGH · 8.8 CVSS v3.1 Published 2023-05-16
Fix available
A fix is available. Upgrade to 113.0.5672.126 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 Autofill UI in Google Chrome on Android prior to 113.0.5672.126 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 the Autofill UI component of Google Chrome on Android versions prior to 113.0.5672.126 allows a remote attacker to exploit heap corruption via a maliciously crafted HTML page.

MitigationUpdate Google Chrome on Android to version 113.0.5672.126 or later. Organizations should use mobile device management to verify browser versions and ensure autofill is disabled for sensitive form fields as a defense-in-depth measure.

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.126
Debian LinuxOperating system
Affected:= 11.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. Identify the installed browser
    Check if Google Chrome or Chromium browser is installed on the device. On Android, go to Settings > Apps > Chrome. On Linux systems, run 'google-chrome --version' or 'chromium --version' in terminal.
    Affected if The browser is Google Chrome or Chromium on Android, Debian 11.0, or Fedora 37/38
  2. Determine the browser version
    On Android, view the Chrome app info to see the version number (e.g., 113.0.5672.x). On Linux, use 'google-chrome --version' or check the installed package version with 'dpkg -l | grep chrome' (Debian) or 'rpm -q chrome-google-beta' (Fedora).
    Affected if The version number is lower than 113.0.5672.126
  3. Confirm the operating system matches affected platforms
    Verify the device is running Google Chrome on Android, or Chrome/Chromium on Debian 11.0 or Fedora 37/38. Check OS version with 'cat /etc/os-release' on Linux.
    Affected if The system is Android with Chrome, or Debian 11.0, or Fedora 37/38 with Chrome installed
  4. Check if Autofill feature is enabled
    On Android Chrome, go to Settings > Passwords and autofill > Google Autofill and verify if it is turned on. On Linux Chrome, check Settings > Autofill and forms > Enable Autofill.
    Affected if Autofill is enabled in Chrome settings (the vulnerability exists in the Autofill UI component)

A user is affected if they are running Google Chrome on Android or Chrome/Chromium on Debian 11.0/Fedora 37/38 with a version lower than 113.0.5672.126 and have Autofill enabled.

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.126 or later
Fixed in 113.0.5672.126
Interim mitigation

Update Google Chrome on Android to version 113.0.5672.126 or later. Organizations should use mobile device management to verify browser versions and ensure autofill is disabled for sensitive form fields as a defense-in-depth measure.

Recommended fix High confidence

Chrome 113.0.5672.126 or later (Android)

  1. 1. Open the Google Chrome app on your Android device
  2. 2. Tap the three-dot menu in the top-right corner
  3. 3. Tap 'Help' and then 'About Chrome'
  4. 4. Chrome will automatically check for updates
  5. 5. If version 113.0.5672.126 or later is available, tap 'Update' to download and install it
  6. 6. Restart Chrome after the update completes

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

Fix this in Chrome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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