CVE-2023-37145
RCE in Totolink Lr350 Firmware 9.3.5u.6369_b20220309
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2023-37145 is a critical-severity Command Injection (CWE-77) vulnerability in Totolink Lr350 Firmware. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 22% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
TOTOLINK LR350 routers running firmware version V9.3.5u.6369_B20220309 contain a command-injection flaw in the setOpModeCfg function. The vulnerability is triggered when an attacker supplies a crafted hostname parameter, allowing arbitrary operating-system commands to be executed on the device. The issue is tracked as CVE-2023-37145 and carries a CVSS 3.1 base score of 9.8.
Because the flaw is reachable over the network without authentication or user interaction, any remote attacker can exploit it to obtain full control of the router. Successful exploitation grants the ability to read, modify, or delete data and to alter device configuration or firmware, corresponding to complete impacts on confidentiality, integrity, and availability.
Public references consist of technical write-ups hosted on GitHub that document the injection vector; no vendor advisory or firmware patch is referenced in the available sources. The EPSS score rose sharply from a low baseline to a peak of 0.2744 in January 2025 before receding to its current value of 0.0140, indicating a period of increased exploitation interest well after the original disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-41065
Vulnerability Data
TOTOLINK LR350 V9.3.5u.6369_B20220309 was discovered to contain a command injection vulnerability via the hostname parameter in the setOpModeCfg function.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.3V1.2.5V1.2.8V1.2.9
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input validation and neutralization that prevent command injection.
Runtime monitoring of software and data can detect anomalous command execution resulting from injection.
Identifying recorded vulnerabilities enables remediation of command-injection flaws before exploitation.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.
Security testing in development catches command-injection vulnerabilities before release.
Secure development life cycle mandates input validation and command construction practices that directly prevent command injection.
Application security requirements explicitly call for controls against injection flaws including command injection.
Secure architecture principles reduce the attack surface but do not prescribe the specific neutralization techniques needed.
Environment separation limits the blast radius of an exploited command injection but does not prevent the flaw itself.