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

> Attackers can bypass permissions via getcfg.php on D-Link DIR-845L routers, potentially accessing restricted functions.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-5x44-874c-9rmj

## What is CVE-2024-33110?

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

### Official description

D-Link DIR-845L router v1.01KRb03 and before is vulnerable to Permission Bypass via the getcfg.php component.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Dlink Dir-845l Firmware.

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

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

## Is CVE-2024-33110 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-36755](https://insights.sbomify.com/CVE-2022-36755/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-36756](https://insights.sbomify.com/CVE-2022-36756/): Command injection in n/a (critical 9.8)
- [CVE-2022-38557](https://insights.sbomify.com/CVE-2022-38557/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2024-29385](https://insights.sbomify.com/CVE-2024-29385/): Command injection in n/a (critical 9.0)
- [CVE-2024-29366](https://insights.sbomify.com/CVE-2024-29366/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-33110 is a critical authentication bypass vulnerability in n/a, published on 6 May 2024. 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-33110 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-33110/ (Markdown: https://insights.sbomify.com/CVE-2024-33110/index.md)
```

## Sources

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

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