CVE-2019-13748 json
Insufficient policy enforcement in developer tools in Google Chrome prior to 79.0.3945.79 allowed a local attacker to obtain potentially se…
published 6y ago modified 4mo ago also EUVD-2019-5165
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.1%
- EPSS 1.1% chance of exploitation in 30 days, percentile 65%
- public exploits
- 0
- none known
Summary
Insufficient policy enforcement in developer tools in Google Chrome prior to 79.0.3945.79 allowed a local attacker to obtain potentially sensitive information from process memory via a crafted HTML page.
Patch / fix
- Google Chrome 79.0.3945.79
- chromium Debian 14, Debian 13, Debian 12 79.0.3945.79-1
debian advisories DEBIAN-CVE-2019-13748
- chromium-browser Ubuntu 16.04 LTS 79.0.3945.79-0ubuntu0.16.04.1
- chromium-browser Ubuntu 18.04 LTS 79.0.3945.79-0ubuntu0.18.04.1
ubuntu advisories UBUNTU-CVE-2019-13748
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-browser RHEL 6 EXTRAS 79.0.3945.79-1.el6_10
red hat advisories RHSA-2019:4238
- chromium openSUSE Tumbleweed 93.0.4577.82-1.1
- chromium openSUSE Tumbleweed 113.0.5672.92-1.1
- chromium Package Hub 15 SP1 79.0.3945.79-bp151.3.35.1
- chromium Package Hub 15, Package Hub 12 SP3, openSUSE Leap 15.1 79.0.3945.79-bp150.252.1
opensuse advisories openSUSE-SU-2024:10681-1openSUSE-SU-2024:12948-1openSUSE-SU-2019:2694-1openSUSE-SU-2019:2692-1
- chromium Arch Linux 79.0.3945.79-1
arch linux advisories AVG-1076
- crbug.com/993706 advisory
Is CVE-2019-13748 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 FencerVendor 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-13748 updated cvss 6.5
chromium-browser: Insufficient policy enforcement in developer tools
-
Red Hat Enterprise Linux Desktop Supplementary (v. 6) chromium-browser 79.0.3945.79-1.el6_10 Red Hat Enterprise Linux HPC Node Supplementary (v. 6) chromium-browser 79.0.3945.79-1.el6_10 Red Hat Enterprise Linux Server Supplementary (v. 6) chromium-browser 79.0.3945.79-1.el6_10 Red Hat Enterprise Linux Workstation Supplementary (v. 6) chromium-browser 79.0.3945.79-1.el6_10fixed: vendor fix RHSA-2019:4238
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.08% chance of exploitation in the next 30 days, higher than 65% 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:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
-
crbug.com
/993706
patch, vendor-advisory
-
access.redhat.com
/errata/RHSA-2019:4238
vendor-advisory, third-party-advisory
-
lists.opensuse.org
/opensuse-security-announce/2019-12/msg00032.html
vendor-advisory, broken-link
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/2Z5M4FPUMDNX2LDPHJKN5ZV5GIS2AKNU/
vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2019-12/msg00036.html
vendor-advisory, broken-link
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/N5CIQCVS6E3ULJCNU7YJXJPO2BLQZDTK/
vendor-advisory
-
debian.org
/security/2020/dsa-4606
vendor-advisory, third-party-advisory
-
security.gentoo.org
/glsa/202003-08
vendor-advisory, third-party-advisory
-
chromereleases.googleblog.com
/2019/12/stable-channel-update-for-desktop.html
vendor-advisory
-
seclists.org
/bugtraq/2020/Jan/27
mailing-list, third-party-advisory
Sources
- CVE List CVE-2019-13748
- NVD CVE-2019-13748
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.