published 11 Jun 2018 · updated 5 Aug 2024
A non-existent chrome.manifest file will attempt to be loaded during startup from the primary installation directory
5.0MediumEPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Firefox 52.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Mozilla | Firefox | <52 | 52 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Firefox, strongest first
Embed
A live severity badge for an advisory, README or ticket