A local privilege escalation vulnerability exists in Thales SafeNet Authentication Client for Windows versions prior to 10.8 R10. The flaw allows a local attacker to execute arbitrary code with SYSTEM privileges, potentially by exploiting improper access controls or insecure handling of privileged operations within the client software.
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 contains a local privilege escalation (LPE) proof-of-concept exploit targeting the Thales SafeNet Authentication Client on Windows. The exploit leverages a race condition in the MSI repair process, specifically by overwriting a temporary executable (wacXXXX.tmp) created in the user's AppData\Local\Temp directory during installation or repair. The main exploit logic is implemented in 'main.cpp', which monitors the temp directory for the creation of the target file and overwrites it with a malicious payload ('raw.exe'). The payload, implemented in 'raw.c', writes a file ('poc.txt') to C:\Users\Public\ to demonstrate successful SYSTEM-level code execution. The repository includes Visual Studio project files for building the exploit and payload. No network endpoints are involved; the attack is purely local and requires the attacker to execute code on the target system. The exploit is a functional proof-of-concept and does not include weaponized features or remote capabilities.
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.