ChromeWeb browser · Google
CVE-2022-2623
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 104.0.5112.79 allowed a remote attacker who convinced a user to engage in specific user interactions to potentially exploit heap corruption via specific UI interactions.
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 prior to 104.0.5112.79. The flaw allows a remote attacker to trigger heap corruption through specific UI interactions after convincing a user to engage in targeted user interactions, potentially leading to arbitrary code execution.
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
< 104.0.5112.79
FedoraOperating system
= 37CVSS 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 Google Chrome is installed on AndroidOpen Chrome on the Android device, tap the three dots menu, go to Settings, and look for Chrome version information in the About Chrome sectionAffected if Google Chrome for Android is installed and running
-
Check the installed Chrome versionIn Chrome on Android, navigate to chrome://version or go to Settings > Help > About Chrome to see the exact version numberAffected if The version number is less than 104.0.5112.79
-
Verify the Offline feature is accessibleIn Chrome on Android, check if Offline pages or Download functionality is enabled by going to Settings > Privacy and Security or looking for download settingsAffected if The Offline/Download feature is present and can be accessed by the user
-
Confirm platform is Android (not desktop)Verify the Chrome browser is running on an Android mobile device rather than a desktop operating systemAffected if The affected product is specifically Chrome on Android, not Chrome on desktop platforms
A user is affected if Google Chrome for Android is installed with a version prior to 104.0.5112.79 and the Offline feature is accessible on the device.
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 · scoped104.0.5112.79
Update Google Chrome for Android to version 104.0.5112.79 or later to patch the use-after-free vulnerability. Organizations should deploy the update via MDM or ensure users update through the Play Store.
Chrome 104.0.5112.79 or later (Chrome 104 stable series)
- For Chrome on Android: Open Google Play Store and update Chrome to version 104.0.5112.79 or later
- For Fedora 37: Run 'sudo dnf update google-chrome-stable' to install the patched package containing the fix
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2623 — 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-2022-2623 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