# CVE-2024-22733: Null dereference in n/a

> Unauthenticated attackers can cause a denial of service on TP-Link MR200 V4 routers via null pointer dereference in the web login panel.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2024
- **Updated:** 5 Nov 2024
- **Also known as:** GHSA-4c48-48vf-pffv

## What is CVE-2024-22733?

CVE-2024-22733 is a low-severity vulnerability in n/a, published on 1 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

TP Link MR200 V4 Firmware version 210201 was discovered to contain a null-pointer-dereference in the web administration panel on /cgi/login via the sign, Action or LoginStatus query parameters which could lead to a denial of service by a local or remote unauthenticated attacker.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Tp-Link Mr200 Firmware.

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

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

## Is CVE-2024-22733 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22733 is a low-severity vulnerability in n/a, published on 1 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22733 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-22733/ (Markdown: https://insights.sbomify.com/CVE-2024-22733/index.md)
```

## Sources

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

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