# CVE-2023-50434: Memory corruption in n/a

> A remote attacker can trigger a stack-based buffer over-read in emDNS by sending malformed DNS requests, potentially causing crashes or leaking memory.

- **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:** 29 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-rmf6-4xgx-9wxc

## What is CVE-2023-50434?

CVE-2023-50434 is a critical memory corruption vulnerability in n/a, published on 29 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

emdns_resolve_raw in emdns.c in emdns through fbd1eef calls strlen with an input that may not be '\0' terminated, leading to a stack-based buffer over-read. This can be triggered by a remote adversary that can send DNS requests to the emdns server. The impact could vary depending on the system libraries, compiler, and processor architecture. Code before be565c3 is unaffected.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2023-50434 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50434 is a critical memory corruption vulnerability in n/a, published on 29 Apr 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-2023-50434 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-2023-50434/ (Markdown: https://insights.sbomify.com/CVE-2023-50434/index.md)
```

## Sources

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

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