Security Resilience

CVE-2023-24138

RCE in Totolink Ca300-Poe Firmware 6.2c.884

Published
03 February 2023
Modified
25 March 2025
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.019 79th percentile
Risk Priority 87 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2023-24138 is a critical-severity Command Injection (CWE-77) vulnerability in Totolink Ca300-Poe Firmware. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 21% 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 CA300-PoE firmware version V6.2c.884 contains a command injection vulnerability in the NTPSyncWithHost function, where unsanitized input to the host_time parameter is passed directly to a system command. The flaw is tracked as CVE-2023-24138 and carries a CVSS 3.1 base score of 9.8, reflecting network-reachable unauthenticated access that can result in full compromise of confidentiality, integrity, and availability. The issue is classified under CWE-77.

An attacker with network access to the device can supply a malicious host_time value that executes arbitrary operating-system commands without authentication or user interaction. Successful exploitation grants the attacker the ability to run code with the privileges of the web-server process, enabling device takeover, configuration changes, or use of the router as an attack pivot.

The EPSS score for this CVE rose from a low baseline after disclosure to a peak of 0.3113 on 2025-01-22 before receding to the current value of 0.1490; this trajectory indicates that exploitation interest increased well after the initial publication. Public references consist of technical write-ups and proof-of-concept material hosted on GitHub that demonstrate the injection vector but do not reference vendor patches or official mitigation guidance.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-24146Same product: Totolink Ca300-Poe
CVE-2023-24144Same product: Totolink Ca300-Poe
CVE-2025-44863Same product: Totolink Ca300-Poe
CVE-2023-24142Same product: Totolink Ca300-Poe
CVE-2023-24161Same product: Totolink Ca300-Poe
CVE-2025-44861Same product: Totolink Ca300-Poe
CVE-2023-24139Same product: Totolink Ca300-Poe
CVE-2023-24160Same product: Totolink Ca300-Poe
CVE-2023-24143Same product: Totolink Ca300-Poe
CVE-2025-44860Same product: Totolink Ca300-Poe

Affected Assets

totolink
ca300-poe firmware
6.2c.884

Mitigating Controls

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.

blocks

A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reduce command injection defects, but leaves a minority slice (e.g. incomplete implementation of those practices, outsourced development without full assurance, or post-SDLC changes) where the weakness can still arise and be exploitable.

blocks

Application security requirements explicitly call for controls against injection flaws including command injection.

blocks

A.8.27 mandates security-by-design principles (e.g. distrust external input, secure session control, data validation/sanitization, least privilege) and design reviews that can stop command injection from being introduced, but this is only a minority slice of CWE-77 because the weakness can still arise in code that bypasses those principles, in non-reviewed components, or in runtime injection vectors the architecture review does not reach.

prevents

Secure coding standards require proper escaping and parameterization of commands, directly eliminating CWE-77.

finds

Security testing in development catches command-injection vulnerabilities before release.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-77, a class-level weakness, and none of its children carries one either.

References