CVE-2018-20073 json
Use of extended attributes in downloads in Google Chrome prior to 72.0.3626.81 allowed a local attacker to read download URLs via the files…
published 2019-06-27 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-12648
- cvss
- 5.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 15%
- public exploits
- 0
- none known
Summary
Use of extended attributes in downloads in Google Chrome prior to 72.0.3626.81 allowed a local attacker to read download URLs via the filesystem.
Patch / fix
- Google Chrome 72.0.3626.81
- chromium Debian 14, Debian 13, Debian 12 72.0.3626.81-1
debian advisories DEBIAN-CVE-2018-20073
- 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.142-bp150.217.1
opensuse advisories openSUSE-SU-2024:10681-1openSUSE-SU-2024:12948-1openSUSE-SU-2019:1815-1
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-2018-20073 updated cvss 6.5
chromium-browser: Inappropriate implementation in downloads
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
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
0.24% chance of exploitation in the next 30 days, higher than 15% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 5.5 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- Google Chrome
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
Sources
- CVE List CVE-2018-20073
- NVD CVE-2018-20073
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.