CVE-2017-5427
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.
Does this matter?
Lower severity and a low EPSS score (0.24%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.0
- 5.5 MEDIUMCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
- EPSS
- 0.24% probability · 15th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-362
- Affected
- mozilla/firefox
- Source
- security@mozilla.org
References
- http://www.securityfocus.com/bid/96692Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037966Third Party Advisory, VDB Entry
- https://bugzilla.mozilla.org/show_bug.cgi?id=1295542Issue Tracking, Patch, Vendor Advisory
- https://www.mozilla.org/security/advisories/mfsa2017-05/Vendor Advisory
- http://www.securityfocus.com/bid/96692Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1037966Third Party Advisory, VDB Entry
- https://bugzilla.mozilla.org/show_bug.cgi?id=1295542Issue Tracking, Patch, Vendor Advisory
- https://www.mozilla.org/security/advisories/mfsa2017-05/Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.