{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-31221 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-31221 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-31221 is a medium-severity authentication bypass vulnerability in LizardByte Sunshine, published on 8 Apr 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-31221 and fix it if it is affected.\n\nWhat it is: CVE-2024-31221 is a medium-severity authentication bypass vulnerability in LizardByte Sunshine, published on 8 Apr 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-31221 in the wild and no public exploit code.\n\nAffected product: LizardByte Sunshine. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-31221/ (Markdown: https://insights.sbomify.com/CVE-2024-31221/index.md)","id":"CVE-2024-31221","markdown":"https://insights.sbomify.com/CVE-2024-31221/index.md","name":"CVE-2024-31221","record":{"aliases":["GHSA-v8gw-jw28-v55m"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Game streaming host","requires_auth":"low_privilege","summary":"Attackers can regain unauthorized access to Sunshine game streaming after unpairing devices if the service is not restarted.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sunshine","vendor":"lizardbyte"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-384","name":"Session Fixation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Clients removed during unpairing process may regain access if Sunshine was not restarted","id":"CVE-2024-31221","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":4,"next":{"headline":"Fides Information Disclosure Vulnerability in Privacy Center of SERVER_SIDE_FIDES_API_URL","id":"CVE-2024-31223"},"packages":[],"prev":{"headline":"Sunshine vulnerable to remote unauthenticated arbitrary file read","id":"CVE-2024-31220"},"products":["Sunshine"],"published":"2024-04-08","related":[{"cvss_score":9.8,"headline":"Sunshine: Authentication bypass via improper client certificate validation","id":"CVE-2026-32253","kev_date_added":null,"published":"2026-05-22"},{"cvss_score":9.7,"headline":"Sunshine application-wide CSRF in the UI leads to command injection as Administrator","id":"CVE-2025-53095","kev_date_added":null,"published":"2025-07-01"},{"cvss_score":7.8,"headline":"LizardBytes Sunshine for Windows contains a DLL search-order hijacking vulnerability","id":"CVE-2025-10198","kev_date_added":null,"published":"2025-09-09"},{"cvss_score":7.8,"headline":"A local privilege escalation vulnerability exists in LizardBytes' Sunshine for Windows","id":"CVE-2025-10199","kev_date_added":null,"published":"2025-09-09"},{"cvss_score":7.7,"headline":"Sunshine improperly enforces pairing protocol request order","id":"CVE-2024-51738","kev_date_added":null,"published":"2025-01-20"},{"cvss_score":7.3,"headline":"Sunshine vulnerable to remote unauthenticated arbitrary file read","id":"CVE-2024-31220","kev_date_added":null,"published":"2024-04-05"},{"cvss_score":6.7,"headline":"SunshineService Has Unquoted Service Path That Allows Local SYSTEM Code Execution","id":"CVE-2025-54081","kev_date_added":null,"published":"2025-09-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-03","vendors":["LizardByte"]},"summary":"Attackers can regain unauthorized access to Sunshine game streaming after unpairing devices if the service is not restarted.","url":"https://insights.sbomify.com/CVE-2024-31221/"}