Loading vulnerability…
CVE-2024-9950 affects Forescout SecureConnector v11.3.07.0109 on Windows. The provided information indicates that the product uses an insecure temporary directory in a way that allows an unauthenticated user to modify compliance scripts. Based on the available description, the flaw stems from unsafe handling of temporary files or directories used to store or stage compliance scripts, enabling unauthorized modification of those scripts before they are consumed or executed by the product. Specific vulnerable functions, code paths, and exact script execution context are not provided in the available content.
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.
This repository is a proof-of-concept (PoC) exploit for CVE-2024-9950, a local privilege escalation vulnerability in Forescout SecureConnector for Windows (versions <= 11.3.07). The exploit targets insecure permissions in a temporary directory used by the SecureConnector agent. The main script (CVE-2024-9950-PoC.ps1) uses PowerShell's FileSystemWatcher to monitor the temp directory for the creation of .bat files. When a targeted .bat file is created, the script renames the original, replaces it with a malicious 'chain_1.bat', and executes it. The payload (chain_1.bat and chain_1.ps1) writes a marker and the output of 'whoami' to a file in C:\Temp, demonstrating code execution with escalated privileges. The repository contains three code files: the main PoC PowerShell script, a batch file launcher, and a PowerShell payload. The attack vector is local, requiring access to the Windows system where SecureConnector is installed. No network endpoints are involved; all actions are performed via the filesystem.
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.
2 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.