CVE-2017-5427: Race Condition
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.
Affected Software
Remediation
Patch Available
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2017-5400
- CVE-2017-5401
- CVE-2017-5402
- CVE-2017-5403
- CVE-2017-5404
- CVE-2017-5406
- CVE-2017-5407
- CVE-2017-5410
- CVE-2017-5411
- CVE-2017-5409
- CVE-2017-5408
- CVE-2017-5412
- CVE-2017-5413
- CVE-2017-5414
- CVE-2017-5415
- CVE-2017-5416
- CVE-2017-5417
- CVE-2017-5425
- CVE-2017-5426
- CVE-2017-5427
- CVE-2017-5418
- CVE-2017-5419
- CVE-2017-5420
- CVE-2017-5405
- CVE-2017-5421
- CVE-2017-5422
- CVE-2017-5399
- CVE-2017-5398
Frequently Asked Questions
What is the severity of CVE-2017-5427?
CVE-2017-5427 is classified as a moderate severity vulnerability.
How do I fix CVE-2017-5427?
To fix CVE-2017-5427, update to a version of Mozilla Firefox that is 52.0 or later.
What type of vulnerability is CVE-2017-5427?
CVE-2017-5427 is a local file inclusion vulnerability.
Who is affected by CVE-2017-5427?
Users of Mozilla Firefox version 52 and earlier are vulnerable to CVE-2017-5427.
Can CVE-2017-5427 be exploited remotely?
CVE-2017-5427 requires local access to exploit, making it a lower-risk vulnerability in terms of remote attacks.