dbcve.org
Dir 600l FirmwareOperating system · Dlink

CVE-2025-4345

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-06
Fix available
A fix is available. Upgrade to after 2.07b01 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A vulnerability was found in D-Link DIR-600L up to 2.07B01 and classified as critical. This issue affects the function formSetLog. The manipulation of the argument host leads to buffer overflow. The attack may be initiated remotely. This vulnerability only affects products that are no longer supported by the maintainer.

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 confidence

Buffer overflow vulnerability in the formSetLog function of D-Link DIR-600L routers (versions up to 2.07B01) when processing the 'host' argument, allowing remote attackers to potentially execute arbitrary code due to improper bounds checking.

MitigationSince the product is end-of-life with no vendor support, network isolation (disabling WAN-facing management) or device replacement is recommended; if the device must remain in service, restrict all remote access and monitor for indicators of compromise.

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
Dir 600l FirmwareOperating system
Affected:<= 2.07b01

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
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 checks

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

  1. Confirm device model is D-Link DIR-600L
    Access the router web interface and check the status page, or use nmap/ssh to query the device model via SNMP or telnet if available. Look for 'DIR-600L' in the device identification.
    Affected if The device is not a D-Link DIR-600L router.
  2. Check firmware version
    In the router web interface, navigate to the status or firmware upgrade page to view the current firmware version. Alternatively, check via command line if telnet/ssh is enabled, or inspect the firmware binary if extracted from the device.
    Affected if The firmware version is 2.07B01 or lower.
  3. Verify web management interface is accessible
    Attempt to access the router's web interface by entering the router's IP address (typically 192.168.0.1) in a browser. Confirm the login page or D-Link administration portal loads.
    Affected if The web interface is not accessible at all (local or remote).
  4. Check if WAN remote management is enabled
    In the router web interface, go to the 'Management' or 'Advanced' settings section and look for 'Remote Management', 'Web Access', or 'WAN Management' settings. Determine if the web interface is reachable from the WAN (internet) side.
    Affected if Remote management from WAN is enabled and the web interface is externally accessible.

A user is affected if they have a D-Link DIR-600L router with firmware version 2.07B01 or lower, and the vulnerable formSetLog function (accessible via the web interface processing the 'host' argument) is available, particularly if WAN remote management is enabled.

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
Upgrade available Upgrade to a release after 2.07b01
Interim mitigation

Since the product is end-of-life with no vendor support, network isolation (disabling WAN-facing management) or device replacement is recommended; if the device must remain in service, restrict all remote access and monitor for indicators of compromise.

Recommended fix High confidence

Replace with a currently supported router (D-Link DIR-600L is end-of-life and no longer receives security updates)

  1. 1. Identify all D-Link DIR-600L devices in the network still running firmware version 2.07b01 or earlier.
  2. 2. Disconnect the affected device from the network to eliminate the vulnerability exploitation vector.
  3. 3. Replace the end-of-life D-Link DIR-600L with a currently supported router from a vendor that provides active security patches.
  4. 4. Configure the new replacement device with strong, unique administrative credentials and WPA3 or WPA2-AES wireless encryption.
  5. 5. Verify the new device is functioning properly and has the latest available firmware installed.
Caveat The D-Link DIR-600L is no longer supported by D-Link; no firmware patch will be released for this vulnerability

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

Fix this in Dir 600l Firmware Scoped from the published advisory
  • Consultation4.0 h
4.0 hours of engineering $800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-4345 — 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-2025-4345 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