ChromeWeb browser · Google
CVE-2019-5822
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 Blink in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to bypass same origin policy 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 (SOP) bypass vulnerability in the Blink rendering engine of Google Chrome (versions prior to 74.0.3729.108). Attackers can exploit this through crafted HTML pages to access resources from different origins, violating the fundamental browser security boundary that normally prevents cross-origin data access.
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
< 74.0.3729.108
Debian LinuxOperating system
= 10.0
FedoraOperating system
= 29= 30= sle-15= 15.0= 15.1= 42.3CVSS 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.
-
Check Google Chrome versionOpen Google Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' in the terminalAffected if The displayed version is lower than 74.0.3729.108
-
Check Chromium version on LinuxRun 'chromium --version' or 'chromium-browser --version' in the terminal if using Chromium instead of ChromeAffected if The displayed version is lower than 74.0.3729.108
-
Check Debian package versionRun 'dpkg -l | grep chromium' or 'dpkg -l | grep google-chrome' to list installed Chrome/Chromium packagesAffected if The installed package version is from Debian 10.0 and is earlier than the fixed version
-
Check Fedora package versionRun 'rpm -qa | grep -i chromium' or 'rpm -qa | grep -i chrome' to list installed browser packagesAffected if The installed package version corresponds to Fedora 29 or 30 and is earlier than the fixed version
-
Check openSUSE package versionRun 'rpm -qa | grep -i chromium' or 'rpm -qa | grep -i chrome' to list installed browser packagesAffected if The installed package version corresponds to openSUSE Leap 15.0, 15.1, 42.3, or Backports sle-15 and is earlier than the fixed version
A user is affected if their installed Google Chrome or Chromium browser version (or the Linux distribution package version) is lower than 74.0.3729.108.
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.
From vendor data74.0.3729.108
Update Google Chrome to version 74.0.3729.108 or later. For enterprise environments, deploy the browser update across all affected workstations and verify the update was applied.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5822 — 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-2019-5822 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