Security Resilience

CVE-2023-2910

RCE in Asustor Data Master 4.0.0.rib4 – 4.0.6.ris1

Published
17 August 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.016 75th percentile
Risk Priority 67 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-2910 is a high-severity Command Injection (CWE-77) vulnerability in Asustor Data Master. Its CVSS base score is 8.8 (High).

Operationally, ranked in the top 25% 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

Improper neutralization of special elements used in a command ('Command Injection') vulnerability in Printer service functionality in ASUSTOR Data Master (ADM) allows remote unauthorized users to execute arbitrary commands via unspecified vectors. Affected products and versions include: ADM 4.0.6.RIS1, 4.1.0…

more

and below as well as ADM 4.2.2.RI61 and below.

CWE(s)

Related Threats

CVEs Like This One

CVE-2026-24933Same product: Asustor Data Master
CVE-2023-3699Same product: Asustor Data Master
CVE-2026-6643Same product: Asustor Data Master
CVE-2026-18186Same product: Asustor Data Master
CVE-2026-24936Same product: Asustor Data Master
CVE-2025-13052Same product: Asustor Data Master
CVE-2026-18187Same product: Asustor Data Master
CVE-2026-3100Same product: Asustor Data Master
CVE-2026-67245Same product: Asustor Data Master
CVE-2026-67244Same product: Asustor Data Master

Affected Assets

asustor
data master
4.0.0.rib4 — 4.0.6.ris1 · 4.1.0.rhu2 — 4.2.3.rk91

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