# CVE-2024-57045: Auth bypass in n/a

> Attackers can bypass authentication on D-Link DIR-859 routers to steal credentials via forged requests, requiring immediate attention from network administrators.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2025
- **Updated:** 19 Feb 2025
- **Also known as:** GHSA-wc7r-hp6q-64m9

## What is CVE-2024-57045?

CVE-2024-57045 is a critical authentication bypass vulnerability in n/a, published on 18 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the D-Link DIR-859 router with firmware version A3 1.05 and earlier permits unauthorized individuals to bypass the authentication. An attacker can obtain a user name and password by forging a post request to the / getcfg.php page.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2024-57045?

It affects 1 product.


Products: Dlink Dir-859 A3 Firmware.

## How do I fix CVE-2024-57045?

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

## Is CVE-2024-57045 being exploited?

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

Public exploit code:

- D-Link DIR-859 - Information Disclosure (nuclei): http/cves/2024/CVE-2024-57045.yaml

## Other vulnerabilities in n/a

- [CVE-2022-25106](https://insights.sbomify.com/CVE-2022-25106/): Memory corruption in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-57045 and fix it if it is affected.

What it is: CVE-2024-57045 is a critical authentication bypass vulnerability in n/a, published on 18 Feb 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-2024-57045 exists.

Affected product: n/a. 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-2024-57045/ (Markdown: https://insights.sbomify.com/CVE-2024-57045/index.md)
```

## Sources

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

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