ChromeWeb browser · Google
CVE-2022-2616
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 · uneditedInappropriate implementation in Extensions API in Google Chrome prior to 104.0.5112.79 allowed an attacker who convinced a user to install a malicious extension to spoof the contents of the Omnibox (URL bar) via a crafted Chrome Extension.
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 confidenceA vulnerability in Google Chrome's Extensions API prior to version 104.0.5112.79 allows a malicious extension installed by an attacker to spoof the contents of the Omnibox (URL bar), potentially deceiving users about the actual URL they are visiting.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check Google Chrome versionNavigate to chrome://settings/help in Chrome, or run 'google-chrome --version' from command line, or check the package manager (e.g., rpm -q google-chrome or dnf list installed google-chrome)Affected if The installed version is older than 104.0.5112.79
-
Check operating system version on FedoraRun 'cat /etc/fedora-release' or 'rpm -E %fedora' to confirm the Fedora versionAffected if Running Fedora 37 with Chrome versions below the fixed release
-
Review installed extensions for untrusted sourcesNavigate to chrome://extensions/ and inspect all enabled extensions. Look for extensions you did not intentionally install, have unknown publishers, or originate from unfamiliar sourcesAffected if Any extension is present that was installed without your explicit consent or from an untrusted source, especially on vulnerable Chrome versions
You are affected if running Google Chrome version older than 104.0.5112.79 AND you have a malicious or untrusted extension installed that could exploit the Omnibox spoofing capability.
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. Users should also be cautious about installing extensions from untrusted sources.
Chrome 104.0.5112.79 or later (any stable channel release)
- Open Chrome and navigate to Settings > Help > About Google Chrome to check the current version
- If the version is below 104.0.5112.79, Chrome will automatically check for and install updates
- Restart Chrome after the update is installed
- On Fedora 37, alternatively run: sudo dnf update google-chrome-stable to receive the latest stable version
- Verify the version is now 104.0.5112.79 or later by returning to Settings > Help > About Google Chrome
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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-2022-2616 — 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-2616 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