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

> An out-of-bounds heap write in Samsung Exynos modems allows remote code execution without authentication via 2G networks.

- **Severity:** High 8.1 (`CVSS:3.1/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2024
- **Updated:** 2 Aug 2024
- **Also known as:** A-307538015, GHSA-wcpq-pw24-jxjp, PUB-A-307538015

## What is CVE-2023-50807?

CVE-2023-50807 is a high-severity memory corruption vulnerability in Samsung Exynos Modem 5300 Firmware, published on 9 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was discovered in Samsung Wearable Processor and Modems with versions Exynos 9110, Exynos Modem 5123, Exynos Modem 5300 that allows an out-of-bounds write in the heap in 2G (no auth).

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 3 products.


Products: Samsung Exynos 9110 Firmware, Samsung Exynos Modem 5123 Firmware, Samsung Exynos Modem 5300 Firmware.

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

Apply the vendor's patch.

## Is CVE-2023-50807 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50807 is a high-severity memory corruption vulnerability in Samsung Exynos Modem 5300 Firmware, published on 9 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-2023-50807 in the wild and no public exploit code.

Affected product: Samsung Exynos Modem 5300 Firmware. 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-50807/ (Markdown: https://insights.sbomify.com/CVE-2023-50807/index.md)
```

## Sources

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

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