LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24152: A command injection vulnerability in the serverIp parameter in the function meshSlaveUpdate of TOTOLINK T8...

A command injection vulnerability in the serverIp parameter in the function meshSlaveUpdate of TOTOLINK T8 V4.1.5cu allows attackers to execute arbitrary commands via a crafted MQTT packet.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This CVE describes a critical flaw in TOTOLINK T8 firmware V4.1.5cu that could let an unauthenticated network attacker run commands on the device. For executives, the risk is loss of control over affected network equipment, with potential confidentiality, integrity, and availability impact.

Executive priority

Treat as urgent where TOTOLINK T8 V4.1.5cu is deployed, especially if reachable by untrusted traffic. Prioritize containment and vendor-fix verification before routine remediation work.

Technical view

The issue is CWE-77 command injection in the serverIp parameter handled by meshSlaveUpdate. The CVE states arbitrary command execution is possible through a crafted MQTT packet. CVSS 3.1 is 9.8, network-accessible, low complexity, no privileges, no user interaction.

Likely exposure

Exposure is likely limited to environments running TOTOLINK T8 V4.1.5cu. Risk increases if the device or its MQTT/control plane can receive traffic from untrusted networks. The source bundle does not provide CPEs, broader affected versions, or default reachability details.

Exploitation context

The CVE reference describes a crafted MQTT packet as the trigger. CISA KEV is false in the provided bundle, and no cited source here confirms active exploitation in the wild.

Researcher notes

Evidence is strong for the reported flaw but incomplete for operational guidance. The source bundle names one affected firmware version, lacks CPE data, and does not identify a patch. Avoid assuming other TOTOLINK models or versions are affected without vendor confirmation.

Mitigation direction

  • Check TOTOLINK guidance for fixed firmware or official mitigation.
  • Restrict MQTT and device management access to trusted networks only.
  • Isolate affected TOTOLINK T8 devices from internet-facing or guest networks.
  • Retire or replace affected devices if no supported fixed firmware exists.
  • Monitor affected network segments for unexpected device configuration or command activity.

Validation and detection

  • Inventory TOTOLINK T8 devices and record firmware versions.
  • Confirm whether any device runs firmware V4.1.5cu.
  • Map whether MQTT or mesh control traffic is reachable from untrusted networks.
  • Review vendor advisories and the CVE record for updated affected-version data.
  • Check security telemetry for suspicious management-plane activity on affected devices.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cwe · medium confidence lookup

CWE-77: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2023-24152 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-24152Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-77 · source CWE mapping

Improper Neutralization of Special Elements used in a Command ('Command Injection')

Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.