LiveActive security incident?Get immediate response
CVE Record

CVE-2023-24140: TOTOLINK CA300-PoE V6.2c.884 was discovered to contain a command injection vulnerability via the NetDiagPin...

TOTOLINK CA300-PoE V6.2c.884 was discovered to contain a command injection vulnerability via the NetDiagPingNum parameter in the setNetworkDiag function.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a critical flaw in TOTOLINK CA300-PoE V6.2c.884 that could let an unauthenticated network attacker run operating-system commands through a diagnostic setting. An exposed device could be fully compromised, affecting confidentiality, integrity, and availability.

Executive priority

Treat as urgent for any exposed or mission-critical TOTOLINK CA300-PoE deployment. The score and unauthenticated network vector justify rapid inventory, isolation, and vendor follow-up even without confirmed active exploitation.

Technical view

CVE-2023-24140 describes command injection (CWE-77) in setNetworkDiag through the NetDiagPingNum parameter. CVSS 3.1 is 9.8 with network attack vector, low complexity, no privileges, no user interaction, and high C/I/A impact. The bundle does not name a vendor patch.

Likely exposure

Exposure is most likely where TOTOLINK CA300-PoE V6.2c.884 devices are deployed and their management or diagnostic interface is reachable from untrusted networks. The CVE metadata has incomplete affected-product fields, so confirm by asset inventory and firmware version checks.

Exploitation context

The provided sources support unauthenticated network reachability and command injection risk. CISA KEV status is false in the bundle, and no cited source confirms active exploitation. The GitHub reference appears vulnerability-focused, but operational exploit details should not be relied on for defensive planning.

Researcher notes

Evidence is concise and incomplete: the CVE names the parameter, function, firmware version, CVSS, and CWE, but affected CPEs and remediation are not populated. Avoid assuming other TOTOLINK models or versions are affected without vendor or test evidence.

Mitigation direction

  • Identify any TOTOLINK CA300-PoE devices and confirm firmware version.
  • Check TOTOLINK guidance for patched firmware or replacement advice.
  • Remove management interfaces from internet and untrusted networks.
  • Restrict access with VPN, firewall rules, and trusted admin subnets.
  • Prioritize replacement if no supported fix is available.

Validation and detection

  • Review asset inventory for TOTOLINK CA300-PoE model names.
  • Verify firmware equals or predates V6.2c.884 where available.
  • Check external attack surface for exposed management services.
  • Inspect logs for unexpected diagnostic function use or admin activity.
  • Document vendor patch status and compensating controls.
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-24140 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-24140Attack 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.