dbcve.org
SunshineApplication · Lizardbyte

CVE-2024-31220

HIGH · 7.3 CVSS v3.1 Published 2024-04-05
Fix available
A fix is available. Upgrade to 0.18.0 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Sunshine is a self-hosted game stream host for Moonlight. Starting in version 0.16.0 and prior to version 0.18.0, an attacker may be able to remotely read arbitrary files without authentication due to a path traversal vulnerability. Users who exposed the Sunshine configuration web user interface outside of localhost may be affected, depending on firewall configuration. To exploit vulnerability, attacker could make an http/s request to the `node_modules` endpoint if user exposed Sunshine config web server to internet or attacker is on the LAN. Version 0.18.0 contains a patch for this issue. As a workaround, one may block access to Sunshine via firewall.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Sunshine versions 0.16.0 through prior to 0.18.0 contain a path traversal vulnerability in the web interface that allows unauthenticated remote attackers to read arbitrary files on the host system. The vulnerability is exploited via HTTP/S requests to the `node_modules` endpoint using directory traversal sequences (e.g., ../../../etc/passwd). This only affects deployments where the Sunshine configuration web UI is exposed outside of localhost.

MitigationUpgrade to Sunshine version 0.18.0 or later. As an interim measure, ensure firewall rules block external access to the Sunshine web interface or restrict access to trusted LAN clients only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SunshineApplication
Affected:>= 0.16.0, < 0.18.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Sunshine version
    Run 'sunshine --version' or check the application metadata/package information to get the exact version number
    Affected if Version is >= 0.16.0 and < 0.18.0
  2. Locate Sunshine configuration file
    Find sunshine.yaml or config.json in the Sunshine configuration directory (typically ~/.config/sunshine/ or /etc/sunshine/)
    Affected if Configuration file exists and web interface is configured
  3. Verify web interface binding address
    Inspect the configuration file for 'web_uiaddr' or similar web interface binding settings. Check if it binds to 0.0.0.0, external IP addresses, or is accessible beyond localhost (127.0.0.1)
    Affected if Web interface binds to 0.0.0.0, external IP, or any address other than 127.0.0.1/localhost
  4. Test node_modules endpoint accessibility
    Send an HTTP GET request to http://<sunshine_host>:47990/node_modules/../../../etc/passwd or similar directory traversal sequence from a remote host
    Affected if Request returns file contents from outside the web root directory

Environment is affected if Sunshine version is between 0.16.0 and 0.18.0 AND the web interface is accessible from addresses other than localhost (127.0.0.1), allowing unauthenticated path traversal attacks via the node_modules endpoint.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.18.0 or later
Fixed in 0.18.0
Interim mitigation

Upgrade to Sunshine version 0.18.0 or later. As an interim measure, ensure firewall rules block external access to the Sunshine web interface or restrict access to trusted LAN clients only.

Recommended fix High confidence

0.18.0

  1. Upgrade Sunshine to version 0.18.0 or later to obtain the patch for this path traversal vulnerability
  2. If you have exposed the Sunshine configuration web interface externally, verify that access is properly restricted through firewall rules
  3. After upgrading, confirm the service is running correctly and the web interface is accessible

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sunshine Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31220 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-31220 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data