CVE-2024-3273VulnerabilityPublished 4 Apr 2024Updated 21 Oct 2025

CVE-2024-3273: D-Link DNS-320L · Command Injection

Affects D-Link DNS-320LSource CVE Database V5

Exploited in the wild · KEV due 2 May 2024 · public detection template (Nuclei) · 99% EPSS · end of life, no fix coming : replace or isolate D-Link DNS-320L; no fix will be released.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score

7.3High

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 2 May 2024 US federal agencies must patch by this date; a sensible deadline for everyone else.
EPSS: 99.9% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: None coming – the product is end of life

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: Low
Availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the impacted component are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

Disclosed: evidence found.
CVE published 4 Apr 2024
Detectable: evidence found.
nuclei template: D-Link Network Attached Storage - Command Injection and Backdoor Account
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 7 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

CVE ID reserved
by VulDB
3 Apr 202418:21 UTC, 7 hours before disclosure
CVE published
on cve.org
4 Apr 202401:00 UTC, t = 0
Added to CISA KEV (opens in a new tab)
exploitation confirmed
11 Apr 2024, 7 days after disclosure
KEV remediation due
US federal deadline
2 May 2024, 28 days after disclosure

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

No fix will be released: D-Link DNS-320L is end of life. Replace it, or isolate it from untrusted networks until you can.

Affected software

Product	Affected	Fixed in
D-Link DNS-320L	Affected =20240403	Fixed in–

Check the firmware or software version for D-Link DNS-320L in the device's admin interface against the vendor advisory.

Description

** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as critical, was found in D-Link DNS-320L, DNS-325, DNS-327L and DNS-340L up to 20240403. Affected is an unknown function of the file /cgi-bin/nas_sharing.cgi of the component HTTP GET Request Handler. The manipulation of the argument system leads to command injection. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The identifier of this vulnerability is VDB-259284. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. NOTE: Vendor was contacted early and confirmed immediately that the product is end-of-life. It should be retired and replaced.

Impact

The impact of CVE-2024-3273 is significant for organizations still operating affected D-Link NAS devices. Successful exploitation allows remote attackers to execute arbitrary commands without authentication, potentially leading to full device compromise. This can result in unauthorized access to sensitive stored data, disruption of file sharing services, and the device being used as a foothold for lateral movement within corporate networks. The compromise of NAS devices can also lead to data exfiltration, ransomware deployment, or destruction of data, impacting confidentiality, integrity, and availability. Since these devices are often connected to internal networks and may store backups or critical files, the risk extends beyond the device itself to the broader organizational infrastructure. The lack of vendor support and patches exacerbates the risk, as vulnerabilities remain unmitigated. Organizations relying on these devices face increased exposure to targeted attacks, especially in sectors where data availability and confidentiality are critical, such as healthcare, education, and small to medium enterprises.

Mitigation

Given the end-of-life status of the affected D-Link NAS devices and absence of patches, the primary mitigation is to retire and replace these devices with supported models that receive security updates. Until replacement is feasible, organizations should isolate these NAS devices from untrusted networks by placing them behind strict firewalls or within segmented VLANs to limit exposure. Disable any unnecessary network services and restrict access to the management interface to trusted IP addresses only. Employ network intrusion detection/prevention systems (IDS/IPS) to monitor for suspicious HTTP requests targeting /cgi-bin/nas_sharing.cgi or unusual command execution patterns. Regularly audit network traffic and device logs for signs of exploitation attempts. If possible, disable the vulnerable CGI functionality or restrict its usage. Implement compensating controls such as strong network segmentation, multi-factor authentication on adjacent systems, and regular backups stored offline to mitigate potential data loss. Finally, educate IT staff about the risks of using unsupported hardware and the importance of timely device lifecycle management.

Summary

CVE-2024-3273 is a command injection vulnerability identified in multiple D-Link NAS devices, specifically DNS-320L, DNS-325, DNS-327L, and DNS-340L, up to firmware version 20240403. The vulnerability resides in an unspecified function within the /cgi-bin/nas_sharing.cgi script, part of the HTTP GET request handler. By manipulating the 'system' argument in the HTTP request, an attacker can inject arbitrary OS commands, which the device executes with the privileges of the web server process. This flaw allows remote, unauthenticated attackers to execute arbitrary commands on the affected device, potentially leading to full system compromise. The vulnerability is classified under CWE-77 (Improper Neutralization of Special Elements used in a Command), indicating improper sanitization of input leading to command injection. The vendor has confirmed these products are end-of-life and no patches will be provided. The CVSS v3.1 base score is 7.3, reflecting network attack vector, low attack complexity, no privileges or user interaction required, and impacts on confidentiality, integrity, and availability. Although no active exploitation has been reported, the public disclosure and availability of exploit details increase the risk of attacks targeting these devices. Given the nature of NAS devices as data storage and sharing points, successful exploitation could lead to data theft, device takeover, or use as a pivot point within internal networks.

CWE-77Improper Neutralization of Special Elements used in a Command ('Command Injection') (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #23OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
Architecture and Design
If at all possible, use library calls rather than external processes to recreate the desired functionality.
Implementation
If possible, ensure that all external commands called from the program are statically created.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
LDAP Injection (opens in a new tab)
Command Delimiters (opens in a new tab)
IMAP/SMTP Command Injection (opens in a new tab)
Manipulating Writeable Terminal Devices (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 28 Feb 2026, 04:41 UTC

Public exploits and detectiona Nuclei detection template

WeaknessesCWE-77

Technical details

References

Community reviews

Related threats