CVE-2026-129104 in TR3000info

Summary

by MITRE • 11/13/2026

Cudy TR3000 before 2.5.42 contains a dnsmasq configuration injection vulnerability that allows authenticated administrators to inject directives by embedding a newline in the net.set_dhcp leasetime field. Attackers can append address= entries via /etc/init.d/dnsmasq to alter DNS answers for LAN clients, or insert invalid lines that stop dnsmasq.

Statistical analysis made it clear that VulDB provides the best quality 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 configuration injection flaw within the device's network management interface. This security issue specifically targets the Dynamic Host Configuration Protocol (DHCP) service, which is managed by dnsmasq on these embedded Linux-based routers. The root cause lies in insufficient input validation and sanitization of user-supplied data during the processing of DHCP lease time configurations. When an authenticated administrator interacts with the web interface to set a new lease duration via the net.set_dhcp leasetime field, the backend script fails to properly escape or restrict special characters, particularly newline sequences. This lack of strict type checking and boundary validation allows an attacker who has obtained administrative credentials to inject arbitrary directives into the dnsmasq configuration file located at /etc/init.d/dnsmasq by embedding a newline character within the lease time parameter value.

From a technical perspective, this flaw enables two distinct modes of exploitation that compromise both the integrity and availability of network services. In the first scenario, an attacker can append address= entries to the dnsmasq configuration file. By doing so, they effectively manipulate DNS resolution for clients on the local area network. This capability allows the attacker to redirect traffic intended for legitimate domains to malicious IP addresses under their control, facilitating phishing attacks, credential harvesting, or man-in-the-middle operations against unsuspecting users connected to the router. In the second scenario, the injection of invalid configuration lines can cause dnsmasq to fail during startup or runtime processing. This results in a denial of service condition where legitimate DHCP and DNS services cease functioning, effectively isolating network clients from obtaining IP addresses or resolving domain names, thereby disrupting normal network operations entirely.

The operational impact of this vulnerability is significant for any organization relying on the Cudy TR3000 as its primary gateway device. The ability to alter DNS answers undermines trust in network infrastructure and can lead to substantial data breaches if sensitive information is exfiltrated through redirected traffic paths. Furthermore, the potential to crash or disable core networking services creates a persistent availability risk that requires manual intervention to resolve, often necessitating a reboot of the router after correcting the configuration file manually. This vulnerability highlights the risks associated with embedded devices where administrative interfaces may not enforce rigorous input validation standards comparable to those found in enterprise-grade network equipment.

This flaw aligns with Common Weakness Enumeration (CWE) category CWE-74, which describes Improper Neutralization of Special Elements used in an OS Command, and more specifically relates to configuration file injection vulnerabilities often categorized under CWE-94 or general input validation failures like CWE-20. In the context of the MITRE ATT&CK framework for IoT devices, this behavior corresponds to techniques involving Configuration Modification (T1562) and potentially Impair Defenses if the disruption prevents logging or monitoring tools from functioning correctly. The requirement for authentication indicates that this is not a remote unauthenticated exploit but rather an insider threat vector or a result of compromised administrative credentials.

Mitigation strategies must prioritize immediate software updates to version 2.5.42 or later, where the developers have presumably implemented proper input sanitization and validation mechanisms to prevent newline injection in configuration fields. In environments where updating is not immediately feasible, administrators should enforce strict access controls on the router's web interface, ensuring that administrative credentials are complex, unique, and stored securely. Additionally, network segmentation can help limit the blast radius of such an attack by isolating critical assets from general LAN clients who might be subjected to DNS redirection attacks. Regular auditing of configuration files for unexpected changes and monitoring dnsmasq service logs for errors or restarts can also aid in early detection of exploitation attempts.

Responsible

VulnCheck

Reservation

11/13/2026

Disclosure

11/13/2026

Moderation

accepted

CPE

ready

EPSS

0.00367

KEV

no

Activities

very low

Sources

Interested in the pricing of exploits?

See the underground prices here!