CVE-2017-5471 json
Memory safety bugs were reported in Firefox 53.
published 8y ago modified 4mo ago also EUVD-2017-14575
- cvss
- 9.8
- version 3.0, 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
Memory safety bugs were reported in Firefox 53. 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 < 54.
Patch / fix
- Mozilla Firefox 54
- firefox Ubuntu 14.04 LTS 54.0+build3-0ubuntu0.14.04.1
- firefox Ubuntu 16.04 LTS 54.0+build3-0ubuntu0.16.04.1
ubuntu advisories UBUNTU-CVE-2017-5471
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 Arch Linux 54.0-1
arch linux advisories AVG-302
Is CVE-2017-5471 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 FencerExploit prediction
1.86% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Mozilla Firefox
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
mozilla.org
/security/advisories/mfsa2017-15/
vendor-advisory
-
bugzilla.mozilla.org
/buglist.cgi?bug_id=1349604%2C1318645%2C1361098%2C1361100%2C1341026%2C1349421%2C1360852%2C1299147%2C1352073%2C
issue-tracking, vendor-advisory
-
securityfocus.com
/bid/99042
vdb-entry, third-party-advisory
-
securitytracker.com
/id/1038689
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2017-5471
- NVD CVE-2017-5471
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.