CVE-2018-18502 json
Mozilla developers and community members reported memory safety bugs present in Firefox 64.
published 2019-02-05 7 y ago modified 2026-06-17 4 mo ago also EUVD-2018-10227
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
Mozilla developers and community members reported memory safety bugs present in Firefox 64. Some of these bugs showed evidence of memory corruption and we presume that with enough effort that some of these could be exploited to run arbitrary code. This vulnerability affects Firefox < 65.
Patch / fix
- Mozilla Firefox 65
- firefox Ubuntu 14.04 LTS 65.0+build2-0ubuntu0.14.04.1
- firefox Ubuntu 16.04 LTS 65.0+build2-0ubuntu0.16.04.1
- firefox Ubuntu 18.04 LTS 65.0+build2-0ubuntu0.18.04.1
ubuntu advisories UBUNTU-CVE-2018-18502
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
- firefox-esr openSUSE Tumbleweed 128.5.1-1.1
- MozillaFirefox openSUSE Tumbleweed 92.0-1.2
opensuse advisories openSUSE-SU-2024:14572-1openSUSE-SU-2024:10600-1
- firefox Arch Linux 65.0-1
arch linux advisories AVG-862
Exploit prediction
2.15% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- Mozilla Firefox
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
usn.ubuntu.com
/3874-1/
vendor-advisory, third-party-advisory
-
mozilla.org
/security/advisories/mfsa2019-01/
vendor-advisory
-
securityfocus.com
/bid/106773
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2018-18502
- NVD CVE-2018-18502
Fencer Vulns 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.