Loading vulnerability…
Local Agent DVR versions thru 6.6.1.0 are vulnerable to directory traversal that allows an unauthenticated local attacker to gain access to sensitive information, cause a server-side forgery request (SSRF), or execute OS commands.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a small Python proof-of-concept exploit set for CVE-2025-63408 affecting iSpy Agent DVR, plus local container helpers for reproducing the issue. The main exploit is path-traversal.py, which uses the requests library to interact directly with AgentDVR’s HTTP API. Its workflow is: check whether camera object oid=1/ot=2 exists via /command/getObject; create a camera with /command/addCamera if needed; invoke /command/addrecording with the attacker-supplied filesystem path as the recording path; wait for the service to restart by polling /login.json; retrieve the resulting file through /streamFile.cgi; then clean up with /q.json?cmd=massdelete. The script defaults to reading /etc/passwd and uses a UUID-suffixed recording name to avoid collisions or crashes noted in the README. This is a real exploit, not just a detector, because it performs end-to-end arbitrary file retrieval from the target. Repository structure is straightforward: README.md briefly documents the exploit and notes that path-traversal.py is a reimplementation of an earlier public PoC; run.py is a Podman-based harness that pulls and runs specific AgentDVR container versions (6.6.1.0, 6.5.8.0, 6.5.1.0) with port 8090 exposed and supporting volumes mounted; shell.py is a convenience wrapper to open /bin/bash inside the running container. Together, run.py and shell.py support local testing, while path-traversal.py is the operational exploit. The exploit is network/web-based, targets the AgentDVR HTTP interface, and its primary capability is arbitrary file read rather than code execution.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.