Loading vulnerability…
A local privilege escalation and code execution vulnerability exists in Fortinet FortiOS versions 5.6.0 to 5.6.2, 5.4.0 to 5.4.8, and 5.2 and below. An attacker with physical access can execute an unauthorized binary from a USB drive by linking it to a command permitted by the fnsysctl CLI command, thereby gaining elevated privileges.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository is a Proof-of-Concept (PoC) exploit for CVE-2017-14187, a local privilege escalation vulnerability in Fortinet FortiOS (versions 5.6.0 to 5.6.2, 5.4.0 to 5.4.8, and below 5.2). The exploit requires physical access to the device and leverages the fnsysctl command and a USB drive to inject a malicious shared object (shell.so) via LD_PRELOAD. The main code file, shell.c, is compiled into a shared object that, when loaded, installs BusyBox utilities to /data2/busybox_bin and spawns a root shell (either ash or bash) for the attacker. The Makefile automates the build process and provides detailed instructions for preparing the USB payload and exploiting the target device. The exploit is intended for debugging and research purposes, as stated in the README and license files. No network endpoints are involved; all actions are performed locally on the device using file paths and binaries provided on the USB drive.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.