9 matches found
VulnCheck KEV: CVE-2023-51833
A command injection issue in TRENDnet TEW-411BRPplus v.2.07eu that allows a local attacker to execute arbitrary code via the data1 parameter in the debug.cgi page...
CVE-2023-51833
A command injection issue in TRENDnet TEW-411BRPplus v.2.07eu that allows a local attacker to execute arbitrary code via the data1 parameter in the debug.cgi page...
CVE-2023-51833
A command injection issue in TRENDnet TEW-411BRPplus v.2.07eu that allows a local attacker to execute arbitrary code via the data1 parameter in the debug.cgi page...
Command injection
A command injection issue in TRENDnet TEW-411BRPplus v.2.07eu that allows a local attacker to execute arbitrary code via the data1 parameter in the debug.cgi page...
PT-2024-14307
Name of the Vulnerable Software and Affected Versions TRENDnet TEW-411BRPplus version 2.07 eu Description A command injection issue exists in TRENDnet TEW-411BRPplus version 2.07 eu that allows a local attacker to execute arbitrary code. This is achieved by manipulating the data1 parameter within...
TRENDnet TEW-411BRPplus Command Injection Vulnerability
The TRENDnet TEW-411BRPplus is a wireless router from Trendnet, Inc. A command injection vulnerability exists in the TRENDnet TEW-411BRPplus version v.2.07eu, which originates from a vulnerability that allows a local attacker to execute arbitrary code via the data1 parameter in the debug.cgi page...
CVE-2023-51833
A command injection issue in TRENDnet TEW-411BRPplus v.2.07eu that allows a local attacker to execute arbitrary code via the data1 parameter in the debug.cgi page...
CVE-2023-51833
Affected product: TRENDnet TEW-411BRPplus router, firmware v2.07_eu. Vulnerability: command injection via the data1 parameter in the debug.cgi page, allowing a local attacker to execute arbitrary code. Root cause: improper handling of user-controlled input in the debug.cgi endpoint. Impact (per s...
CVE-2023-51833
A command injection issue in TRENDnet TEW-411BRPplus v.2.07eu that allows a local attacker to execute arbitrary code via the data1 parameter in the debug.cgi page...