CVE intelligence and bounded remediation

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

Critical CVSS 9.8 CISA KEV

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

Severity
Critical
CVSS
9.8 (3.1)
Published
2024-04-04
CISA KEV
Known exploited
Ecosystem
operating-system
Weaknesses
CWE-798

Affected products

  • dlink / dns-320l_firmware / 1.01.0702.2013
  • dlink / dns-320l_firmware / 1.03.0904.2013
  • dlink / dns-320l_firmware / 1.11
  • dlink / dns-120_firmware
  • dlink / dnr-202l_firmware
  • dlink / dns-315l_firmware

Showing 6 representative product identities from 23 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Authentication bypass and missing authentication

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Map every affected endpoint and protocol path, including alternate ports, legacy routes, recovery flows, service accounts, and machine-to-machine access.
  • Confirm which deployments enable the affected authentication mode and whether the interface is reachable from untrusted networks.
  • Review session, token, credential, and proxy trust configuration without attempting account takeover.

Remediate safely

  • Apply the supported fix and centralize fail-closed authentication before protected request handling.
  • Remove default or embedded credentials, rotate affected secrets and sessions, and bind authentication decisions to the intended audience and channel.
  • Add negative tests for alternate routes, malformed or absent credentials, recovery flows, and proxy-derived identity.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.