Loading vulnerability…
CVE-2022-3368 is a privilege escalation vulnerability in the Software Updater component of Avira Security for Windows. An attacker with write access to the filesystem could exploit this flaw to gain elevated privileges under certain conditions. The vulnerability was addressed in Avira Security version 1.1.72.30556.
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 C++ proof-of-concept exploit for CVE-2022-3368, a vulnerability in the Avira Security software update process on Windows. The exploit leverages Windows junctions (reparse points) and opportunistic locks (oplocks) to perform a time-of-check to time-of-use (TOCTOU) attack. It creates a junction from 'C:\ProgramData\Avira\Security\Temp' to a controlled directory ('C:\expl'), writes a malicious DLL to this directory, and uses oplocks to synchronize the attack. The exploit then triggers the Windows Update process to load the malicious DLL, potentially resulting in code execution as SYSTEM. The main logic is implemented in 'exp/main.cpp', with supporting code in 'FileOplock.cpp/h' and 'def.h'. The repository also contains unrelated helper scripts in the 'old' directory. The exploit is operational and demonstrates a real attack path, but the payload DLL is hardcoded and not easily customizable, so the exploit is not fully weaponized.
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.