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

> Attackers can cause a denial of service in tsMuxer by submitting a crafted MP4 file that triggers a memory leak.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Oct 2023
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-jjxw-34h2-rrhg

## What is CVE-2023-45511?

CVE-2023-45511 is a medium-severity denial of service vulnerability in n/a, published on 12 Oct 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A memory leak in tsMuxer version git-2539d07 allows attackers to cause a Denial of Service (DoS) via a crafted MP4 file.

Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime)

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

It affects 1 product.


Products: Justdan96 Tsmuxer.

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

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

## Is CVE-2023-45511 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-41209](https://insights.sbomify.com/CVE-2024-41209/): Memory corruption in n/a (high 8.8)
- [CVE-2024-49777](https://insights.sbomify.com/CVE-2024-49777/): Memory corruption in n/a (high 8.8)
- [CVE-2024-49778](https://insights.sbomify.com/CVE-2024-49778/): Memory corruption in n/a (high 8.8)
- [CVE-2023-45510](https://insights.sbomify.com/CVE-2023-45510/): Memory corruption in n/a (high 7.5)
- [CVE-2024-41206](https://insights.sbomify.com/CVE-2024-41206/): Information disclosure in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45511 is a medium-severity denial of service vulnerability in n/a, published on 12 Oct 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45511 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-45511/ (Markdown: https://insights.sbomify.com/CVE-2023-45511/index.md)
```

## Sources

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

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