CVE-2023-42801

Stack buffer overflow due to `strcpy` into fixed size buffer in `extractVersionQuadFromString`

HIGH
7.6
CVSS Score
Published: December 14, 2023 at 05:02 PM UTC
Updated: June 17, 2026 at 06:24 AM UTC
8 products affected across 1 vendorMoonlightMoonlight TvMoonlight Embedded

Using moonlight-common-c by moonlight-stream?

Get instant alerts when new vulnerabilities affect moonlight-common-c - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.6
Exploit prediction
EPSS 0.9%

Description

Moonlight-common-c contains the core GameStream client code shared between Moonlight clients. Moonlight-common-c is vulnerable to buffer overflow starting in commit f57bd745b4cbed577ea654fad4701bea4d38b44c. A malicious game streaming server could exploit a buffer overflow vulnerability to crash a moonlight client. Achieving RCE is possible but unlikely, due to stack canaries in use by modern compiler toolchains. The published binaries for official clients Qt, Android, iOS/tvOS, and Embedded are built with stack canaries, but some unofficial clients may not use stack canaries. This vulnerability takes place after the pairing process, so it requires the client to be tricked into pairing to a malicious host. It is not possible to perform using a man-in-the-middle due to public key pinning that takes place during the pairing process. The bug was addressed in commit b2497a3918a6d79808d9fd0c04734786e70d5954.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 0.10.23v < 12.0v < 9.0.0
Affected range stops below 0.10.23, so it looks safe — our inference, not a vendor statement
Affected range stops below 12.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 9.0.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023-10-06, so it looks safe — our inference, not a vendor statement
v < 2.6.1
Affected range stops below 2.6.1, so it looks safe — our inference, not a vendor statement
v < 0.13.4
Affected range stops below 0.13.4, so it looks safe — our inference, not a vendor statement
v < 1.6.0
Affected range stops below 1.6.0, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

7.6HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality
LOW
Integrity
LOW
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-120

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card