CVE-2019-5811 — Google Chrome vulnerability

9 documents7 sources
Severity
8.8HIGHNVD
EPSS
1.0%
top 23.18%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
6
Google ChromeChromiumDebian Linux+3 more
Timeline
PublishedJun 27
Latest updateMay 24

Description

Incorrect handling of CORS in ServiceWorker in Google Chrome prior to 74.0.3729.108 allowed a remote attacker to bypass same origin policy via a crafted HTML page.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitability: 2.8 | Impact: 5.9

Affected Packages5 packages

▶CVEListV5google/chromeunspecified — 74.0.3729.108
▶NVDgoogle/chrome< 74.0.3729.108
▶Debianchromium/chromium< 74.0.3729.108-1+3
▶NVDopensuse/leap15.0, 15.1, 42.3+2
▶NVDopensuse/backportssle-15

Also affects: Debian Linux 10.0, Fedora 29, 30

🔴Vulnerability Details

3
GHSA
GHSA-957j-vpj7-4fcq: Incorrect handling of CORS in ServiceWorker in Google Chrome prior to 74↗2022-05-24
▶
OSV
CVE-2019-5811: Incorrect handling of CORS in ServiceWorker in Google Chrome prior to 74↗2019-06-27
▶
CVEList
CVE-2019-5811: Incorrect handling of CORS in ServiceWorker in Google Chrome prior to 74↗2019-06-27
▶

📋Vendor Advisories

2
Red Hat
chromium-browser: CORS bypass in Blink↗2019-04-23
▶
Debian
CVE-2019-5811: chromium - Incorrect handling of CORS in ServiceWorker in Google Chrome prior to 74.0.3729....↗2019
▶

💬Community

3
Bugzilla
CVE-2019-5811 chromium-browser: CORS bypass in Blink↗2019-04-25
▶
Bugzilla
CVE-2019-5805 CVE-2019-5806 CVE-2019-5807 CVE-2019-5808 CVE-2019-5809 CVE-2019-5810 CVE-2019-5811 CVE-2019-5813 CVE-2019-5814 CVE-2019-5815 CVE-2019-5818 CVE-2019-5819 CVE-2019-5820 CVE-2019-5821 CVE-↗2019-04-25
▶
Bugzilla
CVE-2019-5805 CVE-2019-5806 CVE-2019-5807 CVE-2019-5808 CVE-2019-5809 CVE-2019-5810 CVE-2019-5811 CVE-2019-5813 CVE-2019-5814 CVE-2019-5815 CVE-2019-5818 CVE-2019-5819 CVE-2019-5820 CVE-2019-5821 CVE-↗2019-04-25
▶
CVE-2019-5811 — Google Chrome vulnerability | cvebase