ChromeWeb browser · Google
CVE-2022-2615
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 · uneditedInsufficient policy enforcement in Cookies in Google Chrome prior to 104.0.5112.79 allowed a remote attacker to leak cross-origin data 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 confidenceA Same-Origin Policy bypass in Google Chrome's cookie handling allowed a remote attacker to leak cross-origin data via a crafted HTML page due to insufficient policy enforcement in cookie management.
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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 if Google Chrome is installedOn Windows, look for chrome.exe in Program Files or AppData. On macOS, check /Applications/Google Chrome.app. On Linux, run 'which google-chrome' or check package manager listings.Affected if Google Chrome browser is present on the system
-
Determine installed Chrome versionNavigate to chrome://settings/help in the browser address bar, or run 'google-chrome --version' from command line (Linux/macOS), or check Add/Remove Programs (Windows).Affected if The displayed version number is less than 104.0.5112.79
-
Check Chrome package version on Fedora 37Run 'rpm -q google-chrome' or 'dnf list installed google-chrome' to see the installed RPM package version.Affected if Running Fedora 37 and the installed Chrome package version is earlier than 104.0.5112.79
The environment is affected if Google Chrome version 104.0.5112.79 or earlier is installed, particularly on Fedora 37 systems where the cookie handling SOP bypass could be exploited.
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
- Open Google Chrome and navigate to Settings > Help > About Google Chrome
- Click 'Update Google Chrome' if an update is available, or wait for the automatic update to complete
- Restart the browser after the update completes
- Verify the version by returning to Settings > Help > About Google Chrome and confirming the version is 104.0.5112.79 or later
- For Linux systems (including Fedora), alternatively run: sudo dnf update google-chrome-stable to receive the patched version
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-2615 — 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-2615 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