# CVE-2025-2619: D-Link DAP-1620 Cookie storage check_dws_cookie stack-based overflow

> Remote attackers can trigger a stack-based buffer overflow in the cookie handler of unsupported D-Link DAP-1620 devices to execute arbitrary code.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Mar 2025
- **Updated:** 24 Mar 2025
- **Also known as:** GHSA-2v55-9vh6-3j74

## What is CVE-2025-2619?

CVE-2025-2619 is a critical memory corruption vulnerability in D-Link DAP-1620, published on 22 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in D-Link DAP-1620 1.03. This affects the function check_dws_cookie of the file /storage of the component Cookie Handler. The manipulation leads to stack-based buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-121 (Stack-based Buffer Overflow), CWE-787 (Out-of-bounds Write), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Dlink Dap-1620 Firmware.

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

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

## Is CVE-2025-2619 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2619 exists.

## Other vulnerabilities in D-Link DAP-1620

- [CVE-2025-2618](https://insights.sbomify.com/CVE-2025-2618/): D-Link DAP-1620 Path api set_ws_action heap-based overflow (critical 9.3)
- [CVE-2025-2620](https://insights.sbomify.com/CVE-2025-2620/): D-Link DAP-1620 Authentication storage mod_graph_auth_uri_handler stack-based overflow (critical 9.3)
- [CVE-2025-2621](https://insights.sbomify.com/CVE-2025-2621/): D-Link DAP-1620 storage check_dws_cookie stack-based overflow (critical 9.3)
- [CVE-2021-46381](https://insights.sbomify.com/CVE-2021-46381/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2619 is a critical memory corruption vulnerability in D-Link DAP-1620, published on 22 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2619 exists.

Affected product: D-Link DAP-1620. 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-2619/ (Markdown: https://insights.sbomify.com/CVE-2025-2619/index.md)
```

## Sources

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

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