CVE-2024-10914: Overview on the Vulnerability
A critical security vulnerability has been identified in specific D-LINK NAS devices, This flaw impacts devices up to October 8, 2024, the command injection vulnerability in D-Link network-attached storage (NAS) devices puts over 61,000 internet-connected units at risk of exploitation. highlighting the need for immediate attention and mitigation.
The vulnerability resides in the cgi_user_add
function found within the cgi_bin/accountmgr.ci_cgi_useradd
file. By carefully crafting and manipulating specific data inputs, attackers can exploit this function to execute remote command injection. This flaw enables the execution of arbitrary operating system commands, potentially compromising the entire device and any connected networks.
While the complexity of this exploit is high, requiring advanced technical knowledge to execute, a public exploit has already been released. This significantly increases the risk for users, as it lowers the barrier for exploitation, turning this flaw into a serious threat for unpatched devices.
What are Arbitrary Operating System Commands?
Arbitrary operating system commands refer to any command that can be executed on an operating system, typically at the command-line interface (CLI). These commands are not predefined or limited in scope but rather allow users—or attackers in a security context—to execute any instruction supported by the OS.
In the context of a vulnerability, this means an attacker can:
- Execute System Utilities: Run built-in OS commands like
ls
,cd
,rm
(Linux) ordir
,del
(Windows) to navigate the filesystem, delete files, or modify directories. - Modify System Configurations: Change user permissions, network settings, or configurations critical to the system’s operation.
- Access Sensitive Data: View, copy, or transfer confidential files stored on the system.
- Install Malicious Software: Download and execute malware or backdoor programs for persistent access.
- Control the Device: Take complete control by creating new user accounts, disabling security mechanisms, or shutting down the device.
Why It’s Dangerous
When an attacker gains the ability to run arbitrary OS commands, they can exploit the full power of the operating system. This allows them to bypass authentication, compromise data integrity, and even use the system as a launch point for further attacks on connected devices. This is why vulnerabilities enabling arbitrary command execution are classified as critical.
Affected D-Link NAS Devices
- DNS 320
- DNS 320 LW
- DNS 325
- DNS 340 L
How Can The Vulnerability Be Exploited?
To exploit this vulnerability, an attacker can send a specifically crafted HTTP GET request to the NAS device, embedding malicious input within the name
parameter. Below is an example of such an exploit request:
curl "http://[Target-IP]/cgi-bin/account_mgr.cgi?cmd=cgi_user_add&name=%27;;%27"
This curl request constructs a URL that triggers the cgi_user_add command with a name parameter that includes an injected shell command.
Actual Result

-reference- netsecfish.notion.site
Recommended Fixes
- Firmware Updates: Immediately check for and apply any firmware updates released by D-LINK for the affected models.
- Network Segmentation: Isolate NAS devices from critical systems to limit the impact of any potential breach.
- Monitoring and Logging: Enable logging to detect unusual activity indicative of exploitation attempts.
- Restrict Access: Limit device access to trusted users and IP addresses.
- Disable Unnecessary Features: If possible, disable or restrict the use of the affected
cgi_user_add
function until a fix is applied.
Conclusion
The command injection vulnerability in D-Link NAS devices poses a significant security risk, especially given the availability of a public exploit. While the complexity of the attack may limit immediate exploitation, the critical nature of the flaw, coupled with the widespread use of these devices, demands urgent action. Applying firmware updates, restricting access, and monitoring for suspicious activity are essential steps to protect your NAS devices and prevent unauthorized access. Proactive measures today can mitigate potential breaches and safeguard sensitive data stored on these systems.
References
About SecureMyOrg
At SecureMyOrg, we uncover and fix all possible security vulnerabilities of mobile and web, while providing solutions to mitigate risks. We are trusted by renowned companies like Yahoo, Gojek and Rippling, and with 100% client satisfaction, you’re in safe hands!
Some of the things people reach out to us for –
- Building their cybersecurity program from scratch – setting up cloud security using cost-effective tools, SIEM for alert monitoring, building policies for the company
- Vulnerability Assessment and Penetration Testing ( VAPT ) – We have certified professionals, with certifications like OSCP, CREST – CPSA & CRT, CKA and CKS
- DevSecOps consulting
- Red Teaming activity
- Regular security audits, before product release
- Full time security engineers.
Relevant Posts

ResolverRAT: How to Detect the Stealthy .NET Malware
ResolverRAT is a stealthy .NET RAT that hides in memory and evades detection. Learn how It is uncovered using memory and registry analysis on Windows.

BOLA vs. Other API Vulnerabilities: Why Object-Level Authorization Matters Most
I’m focusing on BOLA, the often-overlooked API vulnerability that can lead to data breaches. Discover why object-level authorization is crucial for API security and how it compares to other vulnerabilities.

Automating BOLA Detection in CI/CD Pipelines in 2025
Automate BOLA detection in CI/CD pipelines for enhanced API security in 2025. Discover tools and techniques to integrate vulnerability scanning and testing.

BOLA in GraphQL APIs: Emerging Risks and How to Mitigate Them
Learn about BOLA risks in GraphQL APIs and how to prevent unauthorized data access. Discover best practices to secure your APIs from emerging threats.

API Authentication and Authorization: From OAuth 2.0 to Zero Trust
Explore the evolution of API authentication and authorization, from OAuth 2.0 to modern Zero Trust models. Learn how to secure APIs in a changing threat landscape.

BOLA vs. BOPLA: Understanding the Differences in API Security
Learn the difference between BOLA and BOPLA vulnerabilities in APIs and how each impacts security. Simple comparison for better understanding.