Loading vulnerability…
A heap-based buffer overflow vulnerability exists in Accfly Wireless Security IR Camera System 720P software versions v3.10.73 through v4.15.77. The vulnerability is present in the CNetClientTalk::OprMsg function, which improperly handles incoming messages, allowing an attacker to trigger a heap overflow without authentication.
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 proof-of-concept (PoC) exploits for four unauthenticated buffer overflow vulnerabilities (CVE-2020-25782 through CVE-2020-25785) in the Accfly Wireless Security Camera firmware (versions V3.10.73 and V4.15.77). The vulnerabilities allow an attacker on the same network (or with MitM/DNS manipulation capabilities) to crash the camera's software or potentially achieve remote code execution. The repository is structured as follows: - Multiple Python scripts (runFtp.py, runGuard.py, runLeak.py, runProtoSet.py, runReboot.py) each target a specific vulnerability or exploitation step. These scripts use the 'pwntools' library to craft and send custom binary protocol packets to the camera's network services. - 'common.py' provides shared functions for packet creation and communication. - 'config.py' defines default IP addresses and ports for the attacker and target device. - The exploits target the camera's unauthenticated TCP/UDP services (notably on ports 23456, 34567, 34568, 34569). No authentication or encryption is required, making exploitation trivial for an attacker with network access. - The PoCs as provided primarily crash the camera's software (denial of service), but the documentation and code indicate that with further development (e.g., using memory leaks), full remote code execution is possible. No hardcoded credentials or external URLs are present; all endpoints are local network IPs and ports. The repository is a well-documented research PoC, not a weaponized exploit.
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.