CVE-2024-3272

KEVD-Link Multiple NAS Devices Use of Hard-Coded Credentials Vulnerability

Description

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.

** 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.

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

PublishedApr 4, 2024

Last modifiedJun 17, 2026

Added to KEVApr 11, 2024

Remediation dueMay 2, 2024

References

github.com/netsecfish/dlinkExploitThird Party Advisory
supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10383Vendor Advisory
vuldb.com/?ctiid.259283Permissions Required
vuldb.com/?id.259283Third Party Advisory
cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-3272US Government Resource

0 recent articles mention this CVE

Risk assessment · Critical

Actively exploited. Patch immediately.

Exploitation: Confirmed in the wild (CISA KEV)
Federal remediation deadline: Overdue by 908 days
CVSS: 9.8 CRITICAL
EPSS (30-day exploit probability): 98.1% · top 1% of all CVEs
Weakness: CWE-798
Attack vector: Network, remotely reachable
Preconditions: No privileges and no user interaction

Recommended actions

1.This vulnerability affects legacy D-Link products. All associated hardware revisions have reached their end-of-life (EOL) or end-of-service (EOS) life cycle and should be retired and replaced per vendor instructions.
2.Treat as emergency change: patch or isolate internet-facing instances first.
3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.

Assessment is derived automatically from the live signals above; verify against your own asset inventory.