Security readout for executives and security teams
Plain-English summary
CVE-2023-37145 is a reported command injection flaw in TOTOLINK LR350 firmware V9.3.5u.6369_B20220309. If an affected router is reachable by an attacker, router-level commands may be possible through the hostname handling path. The supplied sources do not provide CVSS, a vendor fix, or active exploitation evidence.
Executive priority
Treat as a priority for network-edge asset review. Command injection on routers can create meaningful business risk, but urgency depends on whether the named firmware exists in your environment and whether management access is exposed.
Technical view
The CVE describes command injection through the hostname parameter in the setOpModeCfg function on TOTOLINK LR350 V9.3.5u.6369_B20220309. The source bundle does not include affected CPEs, CVSS scoring, CWE mapping, authentication requirements, or a confirmed remediation version.
Likely exposure
Exposure is most likely where TOTOLINK LR350 devices run the named firmware and expose router management or configuration paths to untrusted networks. The bundle does not prove other models or firmware versions are affected.
Exploitation context
The CVE references a public GitHub disclosure, but the provided bundle does not establish active exploitation. It is not listed as CISA KEV in the supplied data.
Researcher notes
Key gaps remain: no CVSS, no CWE, no CPE, no patch reference, and no authentication context in the supplied bundle. Analysis should stay limited to the named TOTOLINK LR350 firmware unless additional vendor or researcher evidence expands scope.
Mitigation direction
- Inventory TOTOLINK LR350 devices and record firmware versions.
- Check TOTOLINK or device supplier guidance for fixed firmware.
- Restrict router administration to trusted networks or VPN only.
- Remove management access from the public internet.
- Consider replacement or isolation if no vendor fix is available.
Validation and detection
- Confirm whether any LR350 device runs V9.3.5u.6369_B20220309.
- Review firewall rules for exposed router management interfaces.
- Check device logs for unexpected configuration changes.
- Monitor CVE and vendor references for remediation updates.
- Document compensating controls for any unfixed devices.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-37145 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.