dbcve.org
Dir 605l FirmwareOperating system · Dlink

CVE-2025-4442

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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-605L 2.13B01. It has been declared as critical. This vulnerability affects the function formSetWAN_Wizard55. The manipulation of the argument curTime leads to buffer overflow. The attack can be initiated remotely. The vendor was contacted early about this disclosure. 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 D-Link DIR-605L router firmware version 2.13B01 within the formSetWAN_Wizard55 function. The vulnerability is caused by insufficient bounds checking on the curTime parameter, which can be manipulated remotely to trigger buffer overflow. This critical flaw (CVSS 9.8) allows remote attackers to potentially execute arbitrary code. Note: This affects an end-of-life product no longer supported by the vendor.

MitigationSince D-Link no longer supports the DIR-605L and will not issue patches, the recommended remediation is to replace affected devices with actively supported hardware. If immediate replacement is not feasible, restrict network access to these devices via firewall rules or network segmentation to reduce attack surface.

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 605l FirmwareOperating system
Affected:= 2.13b01

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
    Access the router web interface at http://192.168.0.1 or check the device label physically. Look for the model number DIR-605L.
    Affected if Device is a D-Link DIR-605L router
  2. Check firmware version via web interface
    Login to the router web interface and navigate to Status or Management section to view the firmware version. The version is typically displayed on the System Info or Device Info page.
    Affected if Firmware version displayed is 2.13B01 exactly
  3. Verify firmware version via telnet if available
    Connect to the router via telnet (if enabled) on port 23 and run the command to display firmware version, commonly 'cat /proc/version' or check /etc/version file.
    Affected if Telnet access returns firmware version 2.13B01
  4. Confirm formSetWAN_Wizard55 endpoint exists
    Examine the router's web interface binaries or HTTP handlers. The vulnerable function formSetWAN_Wizard55 handles WAN setup wizard requests. This is typically exposed via the web interface on /goform/formSetWAN_Wizard55.
    Affected if The router web interface exposes the formSetWAN_Wizard55 endpoint (common on this firmware)
  5. Check if WAN wizard feature is enabled
    Access router web interface and check if the WAN Wizard (initial setup wizard for internet configuration) is accessible or enabled in the management settings.
    Affected if WAN Wizard feature is enabled and accessible on the device

You are affected if you have a D-Link DIR-605L router running firmware version 2.13B01 with the formSetWAN_Wizard55 function exposed on the web interface.

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

Since D-Link no longer supports the DIR-605L and will not issue patches, the recommended remediation is to replace affected devices with actively supported hardware. If immediate replacement is not feasible, restrict network access to these devices via firewall rules or network segmentation to reduce attack surface.

Recommended fix High confidence

N/A - DIR-605L is End-of-Life with no vendor security support; migrate to a currently supported router model

  1. This vulnerability affects D-Link DIR-605L firmware 2.13B01, which D-Link has explicitly stated is no longer supported by the vendor.
  2. No firmware patch or security update is available from D-Link for this end-of-life product.
  3. Replace the affected D-Link DIR-605L device with a currently supported router from D-Link or another vendor that provides active security updates.
  4. If immediate replacement is not possible, place the device behind a properly configured firewall with strict inbound access control lists (ACLs) to limit remote attack surface.
  5. Disable any WAN-facing management interfaces if not required, and restrict access to local network only.
  6. Monitor network traffic for indicators of compromise targeting this vulnerability.
Caveat Device replacement required - legacy DIR-605L has no security patch path

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

Fix this in Dir 605l Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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