CVE intelligence and bounded remediation
CVE-2023-42800 — Moonlight-common-c contains the core GameStream client code shared between Moonlight clients
Moonlight-common-c contains the core GameStream client code shared between Moonlight clients. Moonlight-common-c is vulnerable to buffer overflow starting in commit 50c0a51b10ecc5b3415ea78c21d96d679e2288f9 due to unmitigated usage of unsafe C functions and improper bounds checking. A malicious game streaming server could exploit a buffer overflow vulnerability to crash a moonlight client, or achieve remote code execution (RCE) on the client (with insufficient exploit mitigations or if mitigations can be bypassed). The bug was addressed in commit 24750d4b748fefa03d09fcfd6d45056faca354e0.
- Severity
- High
- CVSS
- 8.8 (3.1)
- Published
- 2023-12-14
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-120
Affected products
- moonlight-stream / moonlight-common-c
- moonlight-stream / moonlight
- moonlight-stream / moonlight / 0.10.22
- moonlight-stream / moonlight_embedded / 2.6.0
- moonlight-stream / moonlight_xbox
- moonlight-stream / moonlight_tv
Showing 6 representative product identities from 10 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.
Matched remediation archetype
Buffer bounds, memory safety, and memory corruption
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Identify affected native-code versions, build flags, architectures, parsers, codecs, drivers, and input paths in all shipped artifacts.
- Determine whether untrusted data reaches the affected routine and the process privilege, sandbox, and network exposure.
- Confirm statically linked, vendored, firmware, and platform-provided copies, not only package-manager records.
Remediate safely
- Apply the maintained upstream correction or replace the affected component, then rebuild every dependent artifact from clean inputs.
- Adopt bounds-checked interfaces, validated sizes and integer conversions, clear ownership, and memory-safe components where practical.
- Enable supported compiler and runtime hardening and add sanitized tests and fuzz regression seeds derived from non-weaponized fixtures.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.