Security readout for executives and security teams
Plain-English summary
CVE-2023-37148 describes a command injection flaw in a TOTOLINK LR350 router firmware build. If reachable and exploitable, this class of bug can let an attacker make the device run unintended system commands. The public bundle does not provide CVSS, authentication requirements, vendor fix details, or active exploitation evidence.
Executive priority
Prioritize discovery and exposure reduction. The issue affects a network edge device class where command injection can be serious, but current evidence is incomplete and no active exploitation is cited in the supplied sources.
Technical view
The CVE states that TOTOLINK LR350 V9.3.5u.6369_B20220309 contains command injection through the `ussd` parameter in the `setUssd` function. The source bundle does not list CWE, CPE, CVSS, affected-version ranges beyond that build, or confirmed patch status. KEV status is false.
Likely exposure
Exposure is limited to environments running the named TOTOLINK LR350 firmware build, especially where the relevant management or USSD function is reachable from untrusted networks. The bundle does not state whether exploitation requires authentication, local network access, or WAN exposure.
Exploitation context
A public researcher reference exists, but the provided sources do not establish real-world exploitation. The CVE is not listed as KEV in the bundle. Treat exploitability details as incomplete unless verified through vendor guidance or controlled internal assessment.
Researcher notes
Key gaps are authentication, attack surface, fixed versions, and affected-version range. Do not generalize beyond TOTOLINK LR350 V9.3.5u.6369_B20220309 from the bundle. The GitHub reference should be treated as public vulnerability research, not proof of active exploitation.
Mitigation direction
- Inventory TOTOLINK LR350 devices and firmware versions.
- Check TOTOLINK or reseller guidance for a fixed firmware or advisory.
- Restrict router management access to trusted administrative networks.
- Remove any unnecessary internet exposure to the affected interface.
- Retire or replace devices if no supported fix is available.
Validation and detection
- Confirm whether any LR350 device runs V9.3.5u.6369_B20220309.
- Verify management interfaces are not exposed to untrusted networks.
- Review device configuration and logs for unexpected administrative activity.
- Track vendor advisories for patch availability or affected-version clarification.
- Use controlled internal testing only; avoid production exploit attempts.
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-37148 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.