Security Resilience

CVE-2024-22663

RCE in Totolink A3700R Firmware 9.1.2u.6165_20211012

Published
23 January 2024
Modified
17 June 2026
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.017 77th percentile
Risk Priority 94 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-2024-22663 is a critical-severity Command Injection (CWE-77) vulnerability in Totolink A3700R Firmware. Its CVSS base score is 9.8 (Critical).

Operationally, ranked in the top 23% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

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 A3700R routers running firmware version V9.1.2u.6165_20211012 contain a command injection vulnerability in the setOpModeCfg function. The flaw is tracked as CVE-2024-22663, carries a CVSS 3.1 score of 9.8, and is categorized under CWE-77. It allows unauthenticated network callers to supply crafted input that is passed directly to a system command interpreter.

An attacker with no credentials or user interaction can send a malicious request to the affected device's web management interface and execute arbitrary operating-system commands. Successful exploitation grants complete control over the device, enabling actions such as configuration changes, traffic interception, or persistence mechanisms.

Public proof-of-concept code demonstrating the setOpModeCfg injection has been published on GitHub. The EPSS score rose from a low baseline to a peak of 0.6009 on 2025-01-22 before receding to its current value of 0.0476, indicating a period of increased exploitation interest after disclosure. No vendor advisory or patch information is referenced in the available sources.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

TOTOLINK_A3700R_V9.1.2u.6165_20211012has a command Injection vulnerability via setOpModeCfg

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-52027Same product: Totolink A3700R
CVE-2024-7160Same product: Totolink A3700R
CVE-2023-46574Same product: Totolink A3700R
CVE-2024-37639Same product: Totolink A3700R
CVE-2025-3666Same product: Totolink A3700R
CVE-2025-3664Same product: Totolink A3700R
CVE-2025-3663Same product: Totolink A3700R
CVE-2024-37631Same product: Totolink A3700R
CVE-2024-37637Same product: Totolink A3700R
CVE-2025-3674Same product: Totolink A3700R

Affected Assets

totolink
a3700r firmware
9.1.2u.6165_20211012

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover command-construction flaws before deployment.

Input validation directly stops construction of commands from untrusted data containing special elements.

Secure engineering principles include proper neutralization and safe command construction practices.

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