Security Resilience

CVE-2024-48659

RCE in Dcnetworks Dcme-320-L Firmware ≤ 9.3.2.114

Published
21 October 2024
Modified
06 November 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.011 66th percentile
Risk Priority 78 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-48659 is a critical-severity Command Injection (CWE-77) vulnerability in Dcnetworks Dcme-320-L Firmware. Its CVSS base score is 9.8 (Critical).

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

CVE-2024-48659 is a command-injection vulnerability (CWE-77) in the DCME-320-L appliance at firmware versions 9.3.2.114 and earlier. The flaw resides in the log_u_umount.php component and carries a CVSS 3.1 base score of 9.8.

An unauthenticated remote attacker can send crafted requests over the network to the affected endpoint and execute arbitrary operating-system commands. Successful exploitation grants full control over the device, allowing disclosure, modification, or destruction of data and services.

The single reference is a public gist containing technical details; no vendor advisory, patch information, or mitigation guidance is supplied in the available data. The EPSS score remains flat at 0.0604 with no material post-disclosure rise.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

An issue in DCME-320-L <=9.3.2.114 allows a remote attacker to execute arbitrary code via the log_u_umount.php component.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-51115Same vendor: Dcnetworks
CVE-2024-52777Same product: Dcnetworks Dcme-320-L
CVE-2024-52780Same product: Dcnetworks Dcme-320-L
CVE-2024-52782Same product: Dcnetworks Dcme-320-L
CVE-2025-9387Same vendor: Dcnetworks
CVE-2026-2000Same vendor: Dcnetworks
CVE-2024-52781Same product: Dcnetworks Dcme-320-L
CVE-2024-52779Same product: Dcnetworks Dcme-320-L
CVE-2024-52778Same product: Dcnetworks Dcme-320-L
CVE-2023-43321Same vendor: Dcnetworks

Affected Assets

dcnetworks
dcme-320-l firmware
≤ 9.3.2.114

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