# CVE-2024-38437: D-Link - CWE-288: Authentication Bypass Using an Alternate Path or Channel

> Attackers can bypass authentication on D-Link DSL-225 devices using an alternate path or channel, gaining unauthorized access.

- **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:** 21 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-fpm3-hh7r-9cg9

## What is CVE-2024-38437?

CVE-2024-38437 is a critical authentication bypass vulnerability in D-Link DSL-225, published on 21 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

D-Link - CWE-288:Authentication Bypass Using an Alternate Path or Channel

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

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

It affects 1 product.


Products: Dlink Dsl-225 Firmware.

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

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

## Is CVE-2024-38437 being exploited?

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

## Other vulnerabilities in D-Link DSL-225

- [CVE-2024-38438](https://insights.sbomify.com/CVE-2024-38438/): D-Link - CWE-294: Authentication Bypass by Capture-replay (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-38437 is a critical authentication bypass vulnerability in D-Link DSL-225, published on 21 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-38437 in the wild and no public exploit code.

Affected product: D-Link DSL-225. 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-38437/ (Markdown: https://insights.sbomify.com/CVE-2024-38437/index.md)
```

## Sources

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

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