ChromeWeb browser · Google
CVE-2022-2603
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 Omnibox in Google Chrome prior to 104.0.5112.79 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.
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 Google Chrome's Omnibox (URL bar) component allows a remote attacker to exploit heap corruption via a crafted HTML page. The vulnerability exists in versions prior to 104.0.5112.79 and could allow arbitrary code execution or renderer process compromise.
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.
-
Verify Google Chrome installationOpen Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' in terminalAffected if Google Chrome is installed on the system
-
Determine installed Chrome versionCheck the version number displayed in chrome://settings/help or via 'google-chrome --version' command outputAffected if The version number is less than 104.0.5112.79 (e.g., 104.0.5112.78, 103.x.x.x, etc.)
-
Confirm OS platformRun 'cat /etc/os-release' on Linux systems to identify the distribution and versionAffected if Running Fedora 37 specifically with an affected Chrome version
-
Check if Omnibox feature is activeThe vulnerability is in the Omnibox (URL bar) component; this is always active in normal Chrome usage - no special config neededAffected if Chrome is used for web browsing with the URL bar present (default configuration)
-
Identify renderer process exposureThis vulnerability can be exploited via crafted HTML pages loaded in the browserAffected if Users can navigate to untrusted web pages (all Chrome users with web access are potentially exposed)
You are affected if Google Chrome version is installed and is lower than 104.0.5112.79, regardless of operating system, as the vulnerability triggers through normal use of the Omnibox when visiting crafted HTML pages.
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 to version 104.0.5112.79 or later to remediate this vulnerability.
Chrome 104.0.5112.79 or later
- 1. Verify current Chrome version by navigating to chrome://settings/help
- 2. Download the latest stable Chrome version from the official Google Chrome website (google.com/chrome) or use the built-in update mechanism
- 3. Install Chrome 104.0.5112.79 or later
- 4. Restart the browser to complete the update
- 5. Verify the version at chrome://settings/help shows 104.0.5112.79 or higher
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
- 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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2603 — 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-2603 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