Skip to content
Fencer Intel
high 8.8

CVE-2019-5827 json

Integer overflow in SQLite via WebSQL in Google Chrome prior to 74.0.3729.131 allowed a remote attacker to potentially exploit heap corrupt…

published 7y ago modified 4mo ago also EUVD-2019-15398

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

Summary

Integer overflow in SQLite via WebSQL in Google Chrome prior to 74.0.3729.131 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page.

Patch / fix

  • Google Chrome 74.0.3729.131
  • sqlite3 Debian 14, Debian 13, Debian 12 3.27.2-3
  • chromium Debian 14, Debian 13, Debian 12 75.0.3770.80-1

debian advisories DEBIAN-CVE-2019-5827

  • sqlite3 Ubuntu 16.04 LTS 3.11.0-1ubuntu1.3
  • sqlite3 Ubuntu 18.04 LTS 3.22.0-1ubuntu0.2
  • chromium-browser Ubuntu 16.04 LTS 74.0.3729.169-0ubuntu0.16.04.1
  • chromium-browser Ubuntu 18.04 LTS 74.0.3729.169-0ubuntu0.18.04.1

ubuntu advisories UBUNTU-CVE-2019-5827

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

  • sqlite RHEL 8 3.26.0-15.el8
  • lemon RHEL 8 3.26.0-15.el8
  • sqlite-libs RHEL 8 3.26.0-15.el8
  • chromium-browser RHEL 6 EXTRAS 74.0.3729.131-1.el6_10

red hat advisories RHSA-2021:4396RHSA-2019:1243

  • chromium openSUSE Tumbleweed 93.0.4577.82-1.1
  • chromium openSUSE Tumbleweed 113.0.5672.92-1.1
  • chromium Package Hub 15, Package Hub 12 SP3, openSUSE Leap 15.1 +1 more 75.0.3770.90-bp150.213.3
  • chromium Package Hub 15 74.0.3729.157-bp150.210.1
  • chromium openSUSE Leap 15.1, openSUSE Leap 15.0 74.0.3729.157-lp151.2.3.1

opensuse advisories openSUSE-SU-2024:10681-1openSUSE-SU-2024:12948-1openSUSE-SU-2019:1666-1openSUSE-SU-2019:1488-1openSUSE-SU-2019:1456-1

  • sqlite AlmaLinux 8 3.26.0-15.el8
  • lemon AlmaLinux 8 3.26.0-15.el8
  • sqlite-libs AlmaLinux 8 3.26.0-15.el8

almalinux advisories ALSA-2021:4396

  • sqlite Rocky Linux 8 3.26.0-15.el8

rocky linux advisories RLSA-2021:4396

Is CVE-2019-5827 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

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-5827 updated cvss 8.8

sqlite: out-of-bounds access due to the use of 32-bit memory allocator interfaces

  • Red Hat Enterprise Linux 6 lemon, sqlite, sqlite-tcl
    affected: no fix planned “Out of support scope”
  • Red Hat Enterprise Linux 7 lemon, sqlite, sqlite-tcl
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux AppStream (v. 8) lemon 3.26.0-15.el8 Red Hat Enterprise Linux BaseOS (v. 8) sqlite 3.26.0-15.el8, sqlite-libs 3.26.0-15.el8
    fixed: vendor fix RHSA-2021:4396
  • Red Hat Enterprise Linux Desktop Supplementary (v. 6) chromium-browser 74.0.3729.131-1.el6_10 Red Hat Enterprise Linux HPC Node Supplementary (v. 6) chromium-browser 74.0.3729.131-1.el6_10 Red Hat Enterprise Linux Server Supplementary (v. 6) chromium-browser 74.0.3729.131-1.el6_10 Red Hat Enterprise Linux Workstation Supplementary (v. 6) chromium-browser 74.0.3729.131-1.el6_10
    fixed: vendor fix RHSA-2019:1243

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

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

Exploits and checks

  • crbug.com https://crbug.com/952406 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/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.