Loading vulnerability…
A heap-based buffer overflow exists in the aswRdr.sys (TDI RDR driver) component of avast! Home and Professional version 4.8.1356.0. The vulnerability is triggered by sending crafted arguments to IOCTL 0x80002024, which can result in memory corruption. This flaw can be exploited locally to cause a denial of service or potentially escalate 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 contains a proof-of-concept (POC) local exploit for CVE-2009-4049, a heap-based buffer overflow vulnerability in the aswRdr.sys (TDI RDR driver) component of avast! Home and Professional 4.8.1356.0 on Windows. The main exploit code is in 'exploit.c', which opens a handle to the device '\\.\GLOBALROOT\Device\ASWRDR' and sends a crafted IOCTL (0x80002024) to trigger memory corruption. The exploit is intended to cause a denial of service (system crash) and, according to the README, does not appear to allow for reliable privilege escalation due to limited control over memory contents. The project is structured as a Visual Studio C project with standard solution and project files, a header file defining the device and IOCTL, and a README describing the vulnerability and exploit limitations. The attack vector is local, requiring the attacker to execute code on the target system.
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.