In the /HNAP1/SetRouterSettings message, the RemotePort parameter is vulnerable, and the vulnerability affects D-Link…
No fixed version listed yet.Check the vendor advisory. References ↓
The RemotePort parameter in the /HNAP1/SetRouterSettings message is vulnerable on D-Link DIR-818LW Rev.A 2.05.B03 and DIR-822 B1 202KRb06 devices, where the value is stored in internal configuration memory without regex validation and then passed unchecked to iptables by the IPTWAN_build_command function. An attacker who can send a crafted SetRouterSettings XML message containing shell metacharacters in the RemotePort element can inject commands into the iptables invocation, with the example given being a payload that starts telnetd.
Official description · CVE.org
In the /HNAP1/SetRouterSettings message, the RemotePort parameter is vulnerable, and the vulnerability affects D-Link DIR-818LW Rev.A 2.05.B03 and DIR-822 B1 202KRb06 devices. In the SetRouterSettings.php source code, the RemotePort parameter is saved in the $path_inf_wan1."/web" internal configuration memory without any regex checking. And in the IPTWAN_build_command function of the iptwan.php source code, the data in $path_inf_wan1."/web" is used with the iptables command without any regex checking. A vulnerable /HNAP1/SetRouterSettings XML message could have shell metacharacters in the RemotePort element such as the `telnetd` string.
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 23 months after disclosure.
- Disclosedday 0
- First seen exploitedVulnCheck KEV evidence+23 mo
What security researchers reported
Not named in any threat report yetAlso mentioned in 1 community threat pulse (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.