dbcve.org
ChromeWeb browser · Google

CVE-2023-4361

MEDIUM · 5.3 CVSS v3.1 Published 2023-08-15
Fix available
A fix is available. Upgrade to 116.0.5845.96 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Inappropriate implementation in Autofill in Google Chrome on Android prior to 116.0.5845.96 allowed a remote attacker to bypass Autofill restrictions via a crafted HTML page. (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

A vulnerability in Google Chrome's Autofill feature on Android (versions prior to 116.0.5845.96) allowed remote attackers to bypass Autofill restrictions through malicious HTML pages. The inappropriate implementation failed to properly enforce Autofill security policies, potentially enabling unauthorized access to saved payment information or personal data in web forms.

MitigationUpdate Google Chrome for Android to version 116.0.5845.96 or later. Organizations should ensure mobile devices receive Chrome updates through their MDM/EMM solutions and verify the installed version.

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.96
Debian LinuxOperating system
Affected:= 11.0= 12.0
FedoraOperating system
Affected:= 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
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

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 Google Chrome version on Android
    Open Chrome app, tap the three dots, go to Settings > About Chrome to view the version number
    Affected if The installed version is lower than 116.0.5845.96
  2. Check Chromium package version on Debian 11
    Run 'dpkg -l | grep chromium' or 'apt show chromium' in terminal to list installed Chromium package version
    Affected if Chromium version is earlier than the version shipped in Chrome 116.0.5845.96 for Debian
  3. Check Chromium package version on Debian 12
    Run 'dpkg -l | grep chromium' or 'apt show chromium' in terminal to list installed Chromium package version
    Affected if Chromium version is earlier than the version shipped in Chrome 116.0.5845.96 for Debian
  4. Check Chromium package version on Fedora 38
    Run 'rpm -qa | grep chromium' or 'dnf info chromium' in terminal to list installed Chromium package version
    Affected if Chromium version is earlier than the version shipped in Chrome 116.0.5845.96 for Fedora
  5. Verify Autofill is enabled on affected Chrome installations
    On Chrome Android, go to Settings > Passwords and Autofill > Autofill service and check if any payment or address autofill services are turned on
    Affected if Autofill for payments or addresses is enabled and the Chrome version is vulnerable

You are affected if Chrome or Chromium version is below 116.0.5845.96 and Autofill services are enabled on the device.

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.96 or later
Fixed in 116.0.5845.96
Interim mitigation

Update Google Chrome for Android to version 116.0.5845.96 or later. Organizations should ensure mobile devices receive Chrome updates through their MDM/EMM solutions and verify the installed version.

Recommended fix High confidence

Chrome 116.0.5845.96 or later

  1. Check current Chrome version by navigating to chrome://settings/help
  2. Update Chrome to version 116.0.5845.96 or later through the browser's built-in update mechanism
  3. For Linux systems (Debian, Fedora), update via system package manager: 'apt update && apt upgrade chromium' (Debian) or 'dnf update chromium' (Federa)
  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
  • 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-4361 — 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-4361 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