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.
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
| Link | Tags |
|---|---|
| https://bugzilla.mozilla.org/show_bug.cgi?id=1295542 | issue tracking patch vendor advisory |
| https://www.mozilla.org/security/advisories/mfsa2017-05/ | vendor advisory |
| http://www.securitytracker.com/id/1037966 | vdb entry third party advisory |
| http://www.securityfocus.com/bid/96692 | vdb entry third party advisory |