CVE-2026-129105 in TR3000
Summary
by MITRE • 11/13/2026
Cudy TR3000 before 2.5.42 contains an option injection vulnerability that allows authenticated administrators to inject arbitrary pppd options by embedding quotes and newlines in L2TP credentials. Attackers can submit crafted usernames or passwords to the net.set_wan RPC method, which l2tp.sh writes into a pppd options file, adding options like logfile to the root pppd process.
Once again VulDB remains the best source for vulnerability data.
Analysis
by VulDB Data Team • 11/13/2026
The vulnerability identified in Cudy TR3000 firmware versions prior to 2.5.42 represents a critical authentication-based command injection flaw within the device's network configuration interface. This security defect specifically targets the L2TP client functionality, which is commonly used for establishing virtual private networks over public internet connections. The root cause lies in insufficient input validation and sanitization mechanisms when processing user-supplied credentials during WAN connection setup. Specifically, the net.set_wan RPC method accepts username and password parameters without adequately escaping special characters such as quotes and newlines before passing them to underlying system scripts like l2tp.sh. This lack of proper encoding allows an authenticated administrator or any attacker who has obtained valid administrative credentials to manipulate how these values are interpreted by the operating system's PPP daemon, pppd.
From a technical perspective, the flaw exploits the way shell scripts handle variable expansion and command execution. When the crafted username or password containing embedded quotes is processed, it breaks out of its intended string context within the configuration file generation logic. By injecting newline characters followed by specific options such as logfile, an attacker can force pppd to execute additional commands with root privileges during the connection initialization phase. This effectively bypasses any sandboxing or restriction that might otherwise limit the scope of actions available through the web interface. The vulnerability falls under CWE-78 Improper Neutralization of Special Elements used in an OS Command and is closely related to CWE-94 Improper Control of Generation of Code, as it allows for arbitrary code execution via configuration file manipulation rather than direct shell command injection strings.
The operational impact of this vulnerability is severe due to the privilege level at which pppd operates. Since PPP daemon processes typically run with elevated system permissions to manage network interfaces and routing tables successfully, successful exploitation grants an attacker full root access to the router's operating system. This compromises not only the confidentiality and integrity of data traversing the L2TP tunnel but also allows for persistent backdoors, malware installation, or use of the device as a pivot point for further attacks against internal network resources. The requirement for authentication does not mitigate risk in many real-world scenarios where default credentials are still used, administrative passwords may be weak or shared across multiple devices, or social engineering tactics can trick administrators into submitting crafted payloads through legitimate-looking configuration forms.
Mitigation strategies must prioritize immediate firmware updates to version 2.5.42 or later, which address the input validation gaps in the l2tp.sh script and related RPC handlers. Until patching is feasible, network segmentation should be enforced to restrict administrative access from untrusted networks, ensuring that only trusted management stations can interact with the device's configuration interfaces. Additionally, enforcing strong, unique passwords for all administrative accounts reduces the likelihood of unauthorized exploitation by external threat actors who might otherwise gain initial foothold through credential stuffing or brute-force attacks. Security monitoring should also be enhanced to detect anomalous network connection attempts involving unusual PPP options or unexpected outbound traffic patterns that could indicate active exploitation of this command injection vector.