# CVE-2024-45407: Sunshine has incorrect state management during pairing process may lead to incorrectly authorized client

> Attackers can bypass authentication during pairing via MITM, gaining unauthorized access to the game streaming host by exploiting incorrect state management.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **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:** 10 Sep 2024
- **Updated:** 10 Sep 2024
- **Also known as:** GHSA-jqph-8cp5-g874

## What is CVE-2024-45407?

CVE-2024-45407 is a medium-severity authentication bypass vulnerability in LizardByte Sunshine, published on 10 Sep 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

Sunshine is a self-hosted game stream host for Moonlight. Clients that experience a MITM attack during the pairing process may inadvertantly allow access to an unintended client rather than failing authentication due to a PIN validation error. The pairing attempt fails due to the incorrect PIN, but the certificate from the forged pairing attempt is incorrectly persisted prior to the completion of the pairing request. This allows access to the certificate belonging to the attacker.

Weakness: CWE-300 (Channel Accessible by Non-Endpoint)

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

It affects 1 product.


Products: Lizardbyte Sunshine.

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

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

## Is CVE-2024-45407 being exploited?

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

## Other vulnerabilities in LizardByte Sunshine

- [CVE-2026-32253](https://insights.sbomify.com/CVE-2026-32253/): Sunshine: Authentication bypass via improper client certificate validation (critical 9.8)
- [CVE-2025-53095](https://insights.sbomify.com/CVE-2025-53095/): Sunshine application-wide CSRF in the UI leads to command injection as Administrator (critical 9.7)
- [CVE-2025-10198](https://insights.sbomify.com/CVE-2025-10198/): LizardBytes Sunshine for Windows contains a DLL search-order hijacking vulnerability (high 7.8)
- [CVE-2025-10199](https://insights.sbomify.com/CVE-2025-10199/): A local privilege escalation vulnerability exists in LizardBytes' Sunshine for Windows (high 7.8)
- [CVE-2024-51738](https://insights.sbomify.com/CVE-2024-51738/): Sunshine improperly enforces pairing protocol request order (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-45407 is a medium-severity authentication bypass vulnerability in LizardByte Sunshine, published on 10 Sep 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-45407 in the wild and no public exploit code.

Affected product: LizardByte Sunshine. 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-45407/ (Markdown: https://insights.sbomify.com/CVE-2024-45407/index.md)
```

## Sources

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

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