Skip to content
Fencer Intel
medium 6.5

CVE-2019-5845 json

Out of bounds access in SwiftShader in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to potentially exploit heap corruption…

published 6y ago modified 4mo ago also EUVD-2019-15416

cvss
6.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

Out of bounds access in SwiftShader in Google Chrome prior to 73.0.3683.75 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Patch / fix

  • Google Chrome 73.0.3683.75
  • chromium Debian 14, Debian 13, Debian 12 73.0.3683.75-1

debian advisories DEBIAN-CVE-2019-5845

  • chromium-browser Ubuntu 16.04 LTS 73.0.3683.75-0ubuntu0.16.04.1
  • chromium-browser Ubuntu 18.04 LTS 73.0.3683.75-0ubuntu0.18.04.1

ubuntu advisories UBUNTU-CVE-2019-5845

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • chromium Package Hub 15 SP1 79.0.3945.117-bp151.3.53.3
  • re2 Package Hub 15 SP1 20200101-bp151.6.12.1
  • chromium Package Hub 15 SP1 79.0.3945.117-bp151.3.47.1
  • re2 Package Hub 15 SP1 20200101-bp151.6.6.1
  • chromium openSUSE Leap 15.1 79.0.3945.117-lp151.2.57.2
  • re2 openSUSE Leap 15.1 20200101-lp151.10.6.1
  • chromium Package Hub 15 SP1, Package Hub 12 SP3 79.0.3945.117-bp151.3.41.1

opensuse advisories openSUSE-SU-2020:0053-1openSUSE-SU-2020:0009-1openSUSE-SU-2020:0006-1openSUSE-SU-2020:0004-1

Is CVE-2019-5845 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.40% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Affected products

  • Google Chrome

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.