IRONSMITHINTEL
CRITICALCVSS9.8
|
Actively Exploited
|CISA KEV|CVE-2024-3272|Auth: none — unauthenticated|Reboot: required|Manual only

D-Link Multiple NAS Devices Use of Hard-Coded Credentials Vulnerability (CVE-2024-3272)

D-Link DNS-320L, DNS-325, DNS-327L, and DNS-340L contains a hard-coded credential that allows an attacker to conduct authenticated command injection, leading to remote, unauthorized code execution.

Published Apr 4, 2024 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve full data confidentiality loss, arbitrary modification of data, complete denial of service or system unavailability. Federal agencies are required to remediate by 2024-05-02 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Use of Hard-coded Credentials (CWE-798) vulnerability in D-Link Multiple NAS Devices. ** UNSUPPORTED WHEN ASSIGNED ** A vulnerability, which was classified as very critical, has been found in D-Link DNS-320L, DNS-325, DNS-327L and DNS-340L up to 20240403. This issue affects some unknown processing of the file /cgi-bin/nas_sharing.cgi of the component HTTP GET Request Handler. The manipulation of the argument user with the input messagebus leads to hard-coded credentials. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-259283. 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. Exploitation requires remote network access, low attack complexity, no authentication required, and no user interaction required.

📧

Phishing link

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

IT Security
Running dns-320l firmware: 1.01.0702.2013, 1.03.0904.2013, 1.11; dns-120 firmware: -; dnr-202l firmware: -; dns-315l firmware: -; dns-320 firmware: -; dns-320lw firmware: -; dns-321 firmware: -; dnr-322l firmware: -; dns-323 firmware: -; dns-325 firmware: 1.01; dns-326 firmware: -; dns-327l firmware: 1.00.0409.2013, 1.09; dnr-326 firmware: -; dns-340l firmware: 1.08; dns-343 firmware: -; dns-345 firmware: -; dns-726-4 firmware: -; dns-1100-4 firmware: -; dns-1200-05 firmware: -; dns-1550-04 firmware: -
Real-world incidentsWhat we've seen

Active exploitation documented in the wild. Threat-research write-up: https://github.com/netsecfish/dlink

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for general installs in scope.
2
Apply the vendor security update referenced in CVE-2024-3272's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.