Security Resilience

CVE-2023-25643

Command Injection in Zte Mc801A Firmware mc801a_elisa3_b19

Published
14 December 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 8.4
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.018 78th percentile
Risk Priority 59 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-25643 is a high-severity Command Injection (CWE-77) vulnerability in Zte Mc801A Firmware. Its CVSS base score is 8.4 (High).

Operationally, ranked in the top 22% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

There is a command injection vulnerability in some ZTE mobile internet products. Due to insufficient input validation of multiple network parameters, an authenticated attacker could use the vulnerability to execute arbitrary commands.

CWE(s)

Related Threats

CVEs Like This One

CVE-2023-25642Same product: Zte Mc801A
CVE-2023-25644Same product: Zte Mc801A
CVE-2023-25649Same vendor: Zte
CVE-2025-26704Same vendor: Zte
CVE-2025-26706Same vendor: Zte
CVE-2026-44407Same vendor: Zte
CVE-2023-41783Same vendor: Zte
CVE-2026-34472Same vendor: Zte
CVE-2024-22063Same vendor: Zte
CVE-2024-22069Same vendor: Zte

Affected Assets

zte
mc801a firmware
mc801a_elisa3_b19
zte
mc801a1 firmware
mc801a1_elisa1_b04

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