# CVE-2024-29192: GHSL-2023-206 gotortc Cross-Site Request Forgery vulnerability

> Cross-site request forgery in go2rtc allows attackers to modify configuration and execute arbitrary commands via the exec handler if the victim visits a malicious site.

- **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:** Yes
- **Published:** 4 Apr 2024
- **Updated:** 29 Aug 2024
- **Also known as:** GHSA-qgj8-g9q4-7f2p, GO-2024-3052

## What is CVE-2024-29192?

CVE-2024-29192 is a high-severity vulnerability in AlexxIT go2rtc, published on 4 Apr 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

gotortc is a camera streaming application. Versions 1.8.5 and prior are vulnerable to Cross-Site Request Forgery. The `/api/config` endpoint allows one to modify the existing configuration with user-supplied values. While the API is only allowing localhost to interact without authentication, an attacker may be able to achieve that depending on how go2rtc is set up on the upstream application, and given that this endpoint is not protected against CSRF, it allows requests from any origin (e.g. a "drive-by" attack) . The `exec` handler allows for any stream to execute arbitrary commands. An attacker may add a custom stream through `api/config`, which may lead to arbitrary command execution. In the event of a victim visiting the server in question, their browser will execute the requests against the go2rtc instance. Commit 8793c3636493c5efdda08f3b5ed5c6e1ea594fd9 adds a warning about secure API access.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/AlexxIT/go2rtc` | Go | All versions | 1.9.0 |
| `github.com/AlexxIT/go2rtc` | Go | All versions | 1.9.0 |
| `github.com/AlexxIT/go2rtc` | Go | All versions | 1.9.0 |

Products: Alexxit Go2rtc.

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

Upgrade github.com/AlexxIT/go2rtc to 1.9.0 or later.

## Is CVE-2024-29192 being exploited?

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

## Other vulnerabilities in AlexxIT go2rtc

- [CVE-2024-29191](https://insights.sbomify.com/CVE-2024-29191/): GHSL-2023-205 gotortc DOM-based Cross-site Scripting vulnerability (medium 6.1)
- [CVE-2024-29193](https://insights.sbomify.com/CVE-2024-29193/): GHSL-2023-207 gotortc DOM-based Cross-site Scripting vulnerability (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-29192 is a high-severity vulnerability in AlexxIT go2rtc, published on 4 Apr 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-29192 exists.

Affected packages and fixed versions:
- github.com/AlexxIT/go2rtc (Go): affected all versions; fixed in 1.9.0
- github.com/AlexxIT/go2rtc (Go): affected all versions; fixed in 1.9.0
- github.com/AlexxIT/go2rtc (Go): affected all versions; fixed in 1.9.0

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

## Sources

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

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