dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-3274

MEDIUM · 5.3 CVSS v3.1 Published 2024-04-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 has been found in D-Link DNS-320L, DNS-320LW and DNS-327L up to 20240403 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file /cgi-bin/info.cgi of the component HTTP GET Request Handler. The manipulation leads to information disclosure. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-259285 was assigned to this vulnerability. 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 · moderate confidence

Information disclosure vulnerability in D-Link DNS-320L, DNS-320LW, and DNS-327L NAS devices affecting the /cgi-bin/info.cgi component. Remote attackers can obtain sensitive information via crafted HTTP GET requests. The vulnerability has a public exploit (VDB-259285).

MitigationDevice retirement and replacement is recommended as the vendor has confirmed end-of-life status with no patches forthcoming. If immediate retirement is not possible, implement strict network access controls and place affected devices behind firewalls to limit exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
Integrity
None
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the device admin interface or check the device label/metadata to confirm the exact model number is DNS-320L, DNS-320LW, or DNS-327L
    Affected if The model is one of DNS-320L, DNS-320LW, or DNS-327L
  2. Confirm device is operational
    Ping the device IP address or attempt HTTP/HTTPS access to verify the device is still powered on and connected to the network
    Affected if The device responds to network requests and is reachable
  3. Verify vulnerable CGI endpoint exists
    Send an HTTP GET request to http://[device-ip]/cgi-bin/info.cgi and observe the response
    Affected if The endpoint returns any output (including error messages), indicating the CGI script is present and accessible
  4. Test for information disclosure
    Send a crafted HTTP GET request to /cgi-bin/info.cgi (using the exploit pattern from VDB-259285 if available) and check if sensitive system information is returned
    Affected if The response contains sensitive information such as system configuration, credentials, or internal network details that should not be publicly accessible
  5. Check firmware version if accessible
    If device admin interface is accessible, navigate to the firmware/version information page to identify the installed firmware version
    Affected if The firmware version matches the affected range for DNS-320L, DNS-320LW, or DNS-327L (compare against any known affected versions)

The environment is affected if a D-Link DNS-320L, DNS-320LW, or DNS-327L device is operational on the network with the /cgi-bin/info.cgi endpoint accessible and responding with sensitive information.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Device retirement and replacement is recommended as the vendor has confirmed end-of-life status with no patches forthcoming. If immediate retirement is not possible, implement strict network access controls and place affected devices behind firewalls to limit exposure.

Recommended fix High confidence
  1. These are end-of-life (EOL) products. D-Link has confirmed these products are no longer supported and should be retired and replaced.
  2. There is no patch or firmware update available for this vulnerability.
  3. Replace affected devices (D-Link DNS-320L, DNS-320LW, DNS-327L) with currently supported hardware.
  4. If immediate replacement is not possible, consider network isolation to limit exposure to remote attackers.

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-3274 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-3274 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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