Command Injection in TOTOLink N600R /setting/setUpgradeFW
CVE-2022-28912 is a command injection vulnerability in TOTOLink N600R firmware version V5.3c.7159_B20190425. The issue was reported in the /setting/setUpgradeFW endpoint, where the filename parameter is insufficiently sanitized before being used in a context that allows execution of operating system commands. An attacker able to reach this functionality can supply a crafted filename value to inject arbitrary shell commands, resulting in command execution on the device.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can allow arbitrary command execution on the affected router. Depending on the privileges of the vulnerable process, this may enable full compromise of the device, including modification of configuration, installation of persistent backdoors, interception or redirection of network traffic, and use of the router as a pivot point for further attacks within the local network.
If you can’t patch tonight, do this now.
Restrict access to the router management interface, especially the firmware upgrade functionality, to trusted administrative networks only. Disable remote administration from untrusted networks or the Internet. Enforce strong administrative credentials, segment management access, and monitor for unexpected configuration changes or command execution artifacts. As an interim measure, prevent exposure of the web administration interface until patched firmware is deployed.
Patch, then assume compromise.
Upgrade to a fixed firmware version from TOTOLink if one is available. The vulnerable code handling the filename parameter in /setting/setUpgradeFW should be corrected to avoid passing user-controlled input to shell command contexts, using strict input validation and safe APIs that do not invoke the shell. If vendor remediation information is not available, replacement of the affected firmware or device may be necessary.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
2 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.