# CVE-2024-31450: Owncast vulnerable to arbitrary file deletion in emoji.go (GHSL-2023-277)

> Administrators can delete arbitrary files on the server via path traversal in the emoji deletion API endpoint.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9355-27m8-h74v, GO-2024-2741

## What is CVE-2024-31450?

CVE-2024-31450 is a low-severity path traversal vulnerability in owncast, published on 19 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Owncast is an open source, self-hosted, decentralized, single user live video streaming and chat server. The Owncast application exposes an administrator API at the URL /api/admin. The emoji/delete endpoint of said API allows administrators to delete custom emojis, which are saved on disk. The parameter name is taken from the JSON request and directly appended to the filepath that points to the emoji to delete. By using path traversal sequences (../), attackers with administrative privileges can exploit this endpoint to delete arbitrary files on the system, outside of the emoji directory. This vulnerability is fixed in 0.1.3.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

3 open source packages ship an affected version, including github.com/owncast/owncast. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/owncast/owncast` | Go | All versions | 0.1.3 |
| `github.com/owncast/owncast` | Go | All versions | 0.1.3 |
| `github.com/owncast/owncast` | Go | All versions | 0.1.3 |

Products: Owncast Project Owncast.

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

Upgrade github.com/owncast/owncast to 0.1.3 or later.

## Is CVE-2024-31450 being exploited?

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

## Other vulnerabilities in owncast

- [CVE-2023-46480](https://insights.sbomify.com/CVE-2023-46480/): OwnCast remote code execution vulnerability (critical 9.8)
- [CVE-2022-3751](https://insights.sbomify.com/CVE-2022-3751/): SQL Injection in owncast/owncast (high 8.8)
- [CVE-2023-3188](https://insights.sbomify.com/CVE-2023-3188/): Server-Side Request Forgery (SSRF) in owncast/owncast (high 8.3)
- [CVE-2024-29026](https://insights.sbomify.com/CVE-2024-29026/): Owncast cross origin request (high 8.2)
- [CVE-2021-39183](https://insights.sbomify.com/CVE-2021-39183/): Unsafe inline XSS Owncast (high 8.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-31450 is a low-severity path traversal vulnerability in owncast, published on 19 Apr 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31450 exists.

Affected packages and fixed versions:
- github.com/owncast/owncast (Go): affected all versions; fixed in 0.1.3
- github.com/owncast/owncast (Go): affected all versions; fixed in 0.1.3
- github.com/owncast/owncast (Go): affected all versions; fixed in 0.1.3

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-31450/ (Markdown: https://insights.sbomify.com/CVE-2024-31450/index.md)
```

## Sources

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

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