# CVE-2023-50433: Denial of service in n/a

> Remote attackers can crash the DHCP server by sending malicious packets that trigger a type confusion and failed memory allocation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Apr 2024
- **Updated:** 1 Nov 2024
- **Also known as:** GHSA-rgc8-28v5-r3w9

## What is CVE-2023-50433?

CVE-2023-50433 is a medium-severity denial of service vulnerability in n/a, published on 29 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

marshall in dhcp_packet.c in simple-dhcp-server through ec976d2 allows remote attackers to cause a denial of service by sending a malicious DHCP packet. The crash is caused by a type confusion bug that results in a large memory allocation; when this memory allocation fails the DHCP server will crash.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2023-50433?


## How do I fix CVE-2023-50433?

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

## Is CVE-2023-50433 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-50433 and fix it if it is affected.

What it is: CVE-2023-50433 is a medium-severity denial of service vulnerability in n/a, published on 29 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-50433 in the wild and no public exploit code.

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-2023-50433/ (Markdown: https://insights.sbomify.com/CVE-2023-50433/index.md)
```

## Sources

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

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