A stack-based buffer overflow exists in the DPC Proxy server (DpcProxy.exe) component of ASUS Remote Console (ARC/ASMB3) versions 2.0.0.19 and 2.0.0.24. The vulnerability is triggered when a remote attacker sends a long string to TCP port 623, resulting in a buffer overflow condition that can be exploited to execute arbitrary code on the target system.
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 single Metasploit module (modules/exploits/windows/misc/asus_dpcproxy_overflow.rb) that exploits a stack buffer overflow vulnerability in Asus Dpcproxy versions 2.0.0.19 up to 2.0.0.23 (CVE-2008-1491) on Windows. The exploit targets the service running on TCP port 623, sending a specially crafted buffer to trigger the overflow and execute arbitrary code. The module allows the user to select a payload (up to 400 bytes, avoiding certain bad characters), which will be executed with the privileges of the vulnerable service. The exploit is operational and can be used to gain remote code execution on affected systems. The code is written in Ruby and is structured as a standard Metasploit exploit module, including all necessary metadata, payload handling, and network communication routines.
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.