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

> A buffer overflow in ReadyMedia allows attackers to execute arbitrary code or cause denial of service via crafted HTTP chunked requests.

- **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:** Yes
- **Published:** 2 Jun 2023
- **Updated:** 8 Jan 2025
- **Also known as:** DEBIAN-CVE-2023-33476, DLA-3465-1, DSA-5434-1, GHSA-xch8-fp3g-32mq, MGASA-2023-0224, UBUNTU-CVE-2023-33476, openSUSE-SU-2024:0093-1, openSUSE-SU-2024:14011-1

## What is CVE-2023-33476?

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

### Official description

ReadyMedia (MiniDLNA) versions from 1.1.15 up to 1.3.2 is vulnerable to Buffer Overflow. The vulnerability is caused by incorrect validation logic when handling HTTP requests using chunked transport encoding. This results in other code later using attacker-controlled chunk values that exceed the length of the allocated buffer, resulting in out-of-bounds read/write.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `minidlna` | SUSE:Package Hub 15 SP5 | All versions | 1.3.3-bp155.2.3.1 |
| `minidlna` | openSUSE:Leap 15.5 | All versions | 1.3.3-bp155.2.3.1 |
| `minidlna` | openSUSE:Tumbleweed | All versions | 1.3.3-2.1 |

Products: Readymedia Project Readymedia.

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

Apply the vendor's patch.

## Is CVE-2023-33476 being exploited?

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

Public exploit code:

- Exploits for a heap overflow in MiniDLNA <=1.3.2 (CVE-2023-33476) (github_poc): https://github.com/mellow-hype/cve-2023-33476

## Other vulnerabilities in n/a

- [CVE-2013-2738](https://insights.sbomify.com/CVE-2013-2738/): SQL injection in n/a (critical 9.8)
- [CVE-2023-47430](https://insights.sbomify.com/CVE-2023-47430/): Memory corruption in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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