CVE-2024-3272
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · unedited** 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceHard-coded credentials vulnerability in D-Link DNS-320L, DNS-325, DNS-327L, and DNS-340L NAS devices. The /cgi-bin/nas_sharing.cgi component accepts the input 'messagebus' via the 'user' parameter in HTTP GET requests, which triggers authentication bypass using hard-coded credentials, allowing remote unauthenticated attackers to gain administrative access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.01.0702.2013= 1.03.0904.2013= 1.11all versionsall versionsall versionsall versionsall versionsall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify your D-Link NAS modelLocate the model number on the device label or check the device status page in the web interfaceAffected if The model is DNS-320L, DNS-325, DNS-327L, DNS-340L, DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320LW, DNS-321, or DNR-322L
-
Check the installed firmware versionLog into the D-Link web interface and navigate to the System or Maintenance section to view the firmware version, or check the device's status pageAffected if For DNS-320L: version is 1.01.0702.2013, 1.03.0904.2013, or 1.11. For other listed models: any firmware version (all versions affected)
-
Verify the web management interface is enabledCheck the device settings to confirm the HTTP/HTTPS web interface is turned on, typically found under Network or System settingsAffected if The web interface is enabled and accessible on the local network or remotely
-
Check network exposure of the nas_sharing.cgi endpointAttempt to access http://[device-ip]/cgi-bin/nas_sharing.cgi?user=messagebus from a browser, or use curl from the command lineAffected if The request returns a response without requiring authentication, indicating the hardcoded credential is exploitable
-
Inspect HTTP response for successful exploitationSend a crafted request with the user parameter set to 'messagebus' and examine if the response contains authenticated content or system informationAffected if The response shows administrative functions, device configuration, or file listing access without providing credentials
You are affected if you own any of the listed D-Link NAS models, particularly DNS-320L at the specified versions or any of the other models at any firmware version, and your device's web interface (specifically the nas_sharing.cgi endpoint) is accessible from your network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImmediate retirement and replacement of affected devices is recommended as they are end-of-life and no longer receive vendor support. If continued operation is mandatory, implement strict network segmentation and firewall rules to block external access to the CGI interface.
- These D-Link NAS devices (DNS-320L, DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320lw, DNS-321, DNR-322L) are end-of-life and no longer receive security updates from the vendor.
- The official description explicitly states: 'It should be retired and replaced' - this is the only secure course of action.
- Immediately decommission affected devices and replace with actively supported hardware from vendors that provide security patches.
- If continued use is absolutely required, isolate the device on a strictly controlled network segment with no external access, and restrict access to only trusted internal users. However, this is not recommended due to the critical severity hard-coded credentials vulnerability.
- Consider data migration to supported NAS solutions from vendors like Synology, QNAP, or Western Digital that provide ongoing security support.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3272 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-3272 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data