# CVE-2024-49778: Memory corruption in n/a

> A heap-based buffer overflow in tsMuxer allows attackers to execute arbitrary code or cause denial of service via a crafted MOV file.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Nov 2024
- **Updated:** 15 Nov 2024
- **Also known as:** GHSA-88h4-j5jq-jm3p

## What is CVE-2024-49778?

CVE-2024-49778 is a high-severity memory corruption vulnerability in n/a, published on 14 Nov 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A heap-based buffer overflow in tsMuxer version nightly-2024-05-12-02-01-18 allows attackers to cause Denial of Service (DoS) and Code Execution via a crafted MOV video file.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2024-49778?

It affects 1 product.


Products: Justdan96 Tsmuxer.

## How do I fix CVE-2024-49778?

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

## Is CVE-2024-49778 being exploited?

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

## 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-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)
- [CVE-2024-41217](https://insights.sbomify.com/CVE-2024-41217/): Memory corruption in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-49778 and fix it if it is affected.

What it is: CVE-2024-49778 is a high-severity memory corruption vulnerability in n/a, published on 14 Nov 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-49778 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-2024-49778/ (Markdown: https://insights.sbomify.com/CVE-2024-49778/index.md)
```

## Sources

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

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