Skip to content
Fencer Intel
medium 5.5

CVE-2017-5427 json

A non-existent chrome.manifest file will attempt to be loaded during startup from the primary installation directory.

published 2018-06-11 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-14531

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 14%
public exploits
0
none known

Summary

A non-existent chrome.manifest file will attempt to be loaded during startup from the primary installation directory. If a malicious user with local access puts chrome.manifest and other referenced files in this directory, they will be loaded and activated during startup. This could result in malicious software being added without consent or modification of referenced installed files. This vulnerability affects Firefox < 52.

Patch / fix

  • Mozilla Firefox 52
  • firefox Ubuntu 14.04 LTS 52.0+build2-0ubuntu0.14.04.1
  • firefox Ubuntu 16.04 LTS 52.0+build2-0ubuntu0.16.04.1

ubuntu advisories UBUNTU-CVE-2017-5427

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 52.0-1

arch linux advisories AVG-194

Exploit prediction

0.24% chance of exploitation in the next 30 days, higher than 14% 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:N/I:H/A:N
NVD 2.0 1.9 AV:L/AC:M/Au:N/C:N/I:P/A:N

Affected products

  • Mozilla Firefox

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

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.