Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
HighCISA KEVExploited in the wildPublic exploit

Command Injection in D-Link DIR-823X /goform/set_prohibiting

IdentifiersCVE-2025-29635CWE-78

CVE-2025-29635 is a command injection vulnerability affecting D-Link DIR-823X routers, including firmware versions 240126 and 240802/24082 as reported in the provided sources. The flaw is present in the router management interface endpoint /goform/set_prohibiting. According to the supplied analysis, attacker-controlled input is incorporated into a shell command via snprintf() and then executed through system() without proper sanitization or validation. Researchers specifically noted that attacker-controlled data reaches the vulnerable code path in a function identified during reverse engineering as sub_42232C, enabling shell metacharacter injection and arbitrary operating system command execution on the device. The issue has been observed in active exploitation by Mirai operators targeting internet-exposed, legacy/end-of-life DIR-823X devices.

Share:
For your environment

Are you exposed to this one?

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.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote execution of arbitrary OS commands on the affected router. In observed attacks, this was used to download and execute a shell script that installed the Mirai variant tuxnokill, enabling botnet enrollment and DDoS activity. More broadly, compromise of the router can permit full device takeover, malicious configuration changes, persistence, traffic interception, use of the device as a staging point for further attacks, and potential lateral movement into adjacent networks reachable from the router.

Mitigation

If you can’t patch tonight, do this now.

If immediate replacement or patching is not possible, disable remote administration and prevent exposure of the management interface to the internet. Restrict access to the administrative interface to trusted internal hosts or management networks only, using firewall/ACL controls. Change default or weak administrator credentials, monitor for unexpected configuration changes, and inspect devices for signs of compromise such as suspicious outbound connections, downloaded scripts, or unknown processes. Given active exploitation and Mirai botnet targeting, internet-exposed end-of-life devices should be treated as high risk and isolated or retired as soon as possible.

Remediation

Patch, then assume compromise.

Apply the latest D-Link firmware update if a fixed release is available for the affected DIR-823X model and firmware branch. Because the provided content repeatedly describes the affected devices as legacy/end-of-life and indicates a vendor fix may be unavailable, the primary remediation for unsupported units is replacement with a supported router model. Organizations should inventory exposed DIR-823X devices, remove them from service where possible, and validate that no unauthorized scripts, binaries, or configuration changes remain on previously exposed systems.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
D-LinkDir-823xhardware
D-LinkDir-823x Firmwareoperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware15

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity38

Community discussion across Reddit, Mastodon, and other social sources.