# CVE-2025-4441: D-Link DIR-605L formSetWAN_Wizard534 buffer overflow

> Remote attackers can exploit a buffer overflow in the WAN wizard to execute arbitrary code on unsupported D-Link DIR-605L routers.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2025
- **Updated:** 9 May 2025
- **Also known as:** GHSA-jx33-373q-67x5

## What is CVE-2025-4441?

CVE-2025-4441 is a high-severity memory corruption vulnerability in Dlink Dir-605l Firmware, published on 8 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in D-Link DIR-605L 2.13B01. It has been classified as critical. This affects the function formSetWAN_Wizard534. The manipulation of the argument curTime leads to buffer overflow. It is possible to initiate the attack remotely. The vendor was contacted early about this disclosure. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-4441?

It affects 1 product.


Products: Dlink Dir-605l Firmware.

## How do I fix CVE-2025-4441?

No fix has been published for CVE-2025-4441 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-4441 being exploited?

There is no known exploitation of CVE-2025-4441 in the wild and no public exploit code.

## Other vulnerabilities in Dlink Dir-605l Firmware

- [CVE-2021-40655](https://insights.sbomify.com/CVE-2021-40655/): D-Link DIR-605 Router Information Disclosure (high 7.5, exploited in the wild)
- [CVE-2026-42373](https://insights.sbomify.com/CVE-2026-42373/): D-Link DIR-605L B2 Hardcoded Telnet Backdoor Credentials (critical 9.8)
- [CVE-2023-29961](https://insights.sbomify.com/CVE-2023-29961/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-24348](https://insights.sbomify.com/CVE-2023-24348/): Memory corruption in n/a (critical 9.8)
- [CVE-2023-24349](https://insights.sbomify.com/CVE-2023-24349/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-4441 and fix it if it is affected.

What it is: CVE-2025-4441 is a high-severity memory corruption vulnerability in Dlink Dir-605l Firmware, published on 8 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-4441 in the wild and no public exploit code.

Affected product: Dlink Dir-605l Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-4441/ (Markdown: https://insights.sbomify.com/CVE-2025-4441/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-4441
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-4441
- OSV: https://osv.dev/vulnerability/CVE-2025-4441

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-4441/
Summaries are generated and may contain mistakes; the official description above is the record.