ChromeWeb browser · Google
CVE-2023-2312
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 · uneditedUse after free in Offline in Google Chrome on Android prior to 116.0.5845.96 allowed a remote attacker who had compromised the renderer process 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 confidenceUse-after-free vulnerability in the Offline feature of Google Chrome on Android versions before 116.0.5845.96. A remote attacker with a compromised renderer process can exploit heap corruption via a crafted HTML page.
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
< 116.0.5845.96CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm the browser is Google Chrome on AndroidCheck the app name and version in Android Settings > Apps > Chrome. Verify the package name is 'com.android.chrome' and the OS is Android, not iOS or desktop.Affected if The browser is not Google Chrome on Android (for example, Samsung Internet, Firefox, or Chrome on desktop/iOS are not affected)
-
Check the installed Chrome versionOpen Chrome on Android, tap the three-dot menu > Help > About Chrome. The version number is displayed at the top.Affected if The displayed version is earlier than 116.0.5845.96 (for example, 115.x.x.x or earlier)
-
Verify the Chrome update statusIn the About Chrome screen, check if an update is available. If 'Chrome is up to date' appears with version 116.0.5845.96 or later, the vulnerability is patched.Affected if Chrome reports it is up to date with a version below 116.0.5845.96, or cannot check for updates
You are affected if you are running Google Chrome on Android with a version earlier than 116.0.5845.96.
Generated from the published advisory. Verify against your own configuration.
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 · scoped116.0.5845.96
Update Google Chrome on Android to version 116.0.5845.96 or later. For enterprise environments, ensure managed devices receive the Chrome update through your mobile device management (MDM) solution.
Chrome 116.0.5845.96 or later for Android
- Open the Google Play Store app on the Android device
- Search for 'Google Chrome' or locate it in installed apps
- Tap 'Update' to install Chrome version 116.0.5845.96 or later
- Alternatively, enable auto-updates for Chrome in Play Store settings to receive future security updates automatically
- After updating, verify the Chrome version by navigating to chrome://settings/help to confirm the version is 116.0.5845.96 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2312 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-2312 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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