Skip to content

Incorrect state management during pairing process may lead to incorrectly authorized client

Moderate
cgutman published GHSA-jqph-8cp5-g874 Sep 10, 2024

Package

Sunshine

Affected versions

>= 5fcd07ecb1428bfe245ad6fa349aead476c7e772

Patched versions

v2024.910.1354, >= fd7e68457a134102d1b30af5796c79f2aa623224

Description

Impact

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.

This may result when:

  1. The user attempts to pair to Sunshine using Moonlight or another client.
  2. An attacker performs a MITM attack this legitimate pairing attempt by forwarding a forged pairing request with a new PIN and attacker's certificate to the host PC.
  3. The user types the original PIN from the legitimate pairing attempt into the Sunshine UI.

Expected result:
The pairing attempt fails due to the incorrect PIN and no new clients are authorized.

Actual result:
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.

Affected Versions and Patches

There are no affected stable release builds.

Pre-release Sunshine builds between the merge of PR #2042 (May 27, 2024 20:43 UTC) and fd7e684 (September 10, 2024 00:14 UTC) are affected.

Patch: fd7e684

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

CVE ID

CVE-2024-45407

Weaknesses

Credits