dbcve.org
Dir 600l FirmwareOperating system · Dlink

CVE-2025-4348

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. It has been rated as critical. Affected by this issue is the function formSetWanL2TP. The manipulation of the argument host leads to buffer overflow. The attack may be launched 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

A buffer overflow vulnerability exists in the formSetWanL2TP function of D-Link DIR-600L wireless routers (firmware up to 2.07B01). The overflow occurs when processing the 'host' argument during L2TP VPN configuration, allowing remote attackers to potentially execute arbitrary code due to inadequate input validation.

MitigationSince D-Link DIR-600L is end-of-life with no vendor support, immediate mitigation requires disabling L2TP functionality if unused, implementing network segmentation to isolate the device, and planning for replacement with a currently supported router. If L2TP is required, restrict access via firewall rules to authorized management IPs only.

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. Identify device model
    Check the router label or web interface to confirm the device is a D-Link DIR-600L. Access the router admin panel (typically at 192.168.0.1) and look for the model number in the status or system information page.
    Affected if Device is not a D-Link DIR-600L
  2. Check firmware version
    In the router web interface, navigate to the Administration or System section and locate the firmware version information. Compare the installed version to 2.07b01 (any version equal to or below 2.07b01 is affected).
    Affected if Firmware version is 2.07b01 or lower, or if the version cannot be determined but is within the listed affected range
  3. Verify L2TP VPN status
    In the router web interface, navigate to the WAN or VPN settings section. Look for L2TP (Layer 2 Tunneling Protocol) configuration options. Check whether L2TP is enabled or configured for VPN connections.
    Affected if L2TP functionality is enabled or configured on the device
  4. Check for remote access exposure
    Determine if the router's web management interface is exposed to the internet (check port forwarding rules, firewall settings, or WAN-facing IP access). The vulnerability is exploitable remotely via the 'host' argument in L2TP configuration.
    Affected if Router admin interface or L2TP settings are accessible from the internet (WAN side)

The device is affected if it is a D-Link DIR-600L running firmware version 2.07b01 or lower AND has L2TP VPN functionality enabled, especially if the management interface is exposed to the internet.

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 D-Link DIR-600L is end-of-life with no vendor support, immediate mitigation requires disabling L2TP functionality if unused, implementing network segmentation to isolate the device, and planning for replacement with a currently supported router. If L2TP is required, restrict access via firewall rules to authorized management IPs only.

Recommended fix High confidence
  1. 1. Replace the D-Link DIR-600L device with a currently supported model, as this device is end-of-life and no longer receives firmware updates from D-Link.
  2. 2. If immediate replacement is not possible, restrict network access to the device's management interface by placing it behind a firewall or VPN, limiting exposure to local networks only.
  3. 3. Disable the L2TP WAN configuration feature if not needed, or restrict access to the web management interface to trusted IP addresses only.
  4. 4. Monitor the device for any signs of compromise and plan for hardware replacement as soon as feasible.
Caveat Device is end-of-life with no available firmware updates; replacement is the only reliable remediation

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,820
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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