Star Wars Episode I: Racer multiplayer flaw allows remote code execution
Original title: Finding a vulnerability in Star Wars Episode I: Racer
The write-up examines the GOG Windows 1.0 build, which discovers games over UDP port 54792 using DirectPlay.
Synacktiv researchers analyzed local-network multiplayer in Star Wars Episode I: Racer version 1.0, the Windows build distributed by GOG. The game uses Microsoft DirectPlay and sends discovery traffic to the local broadcast address. The introduction says the research includes a vulnerability that allows remote code execution, a Wireshark dissector, and DirectPlay tooling. The provided excerpt ends during protocol reverse engineering.
Unconfirmed: The excerpt ends before the flaw's trigger, full impact, and any fix are described.
- Research focused on version 1.0 distributed by GOG for Windows.
- Multiplayer traffic uses UDP destination port 54792.
- The DirectPlay marker appears at offset 27, so Wireshark's heuristic misses it.
- The binary instantiates IDirectPlay4 and selects the IPX service provider.
Impact: Remote code execution through the multiplayer protocol.
| Product | Affected |
|---|---|
| LucasArts Star Wars Episode I: Racer | version 1.0, GOG Windows build |
- Vendors
- LucasArts
- Products
- Star Wars Episode I: Racer
From the original article
15 min read at synacktiv.com
Star Wars Episode I: Racer is a racing video game published by LucasArts. The player pilots a podracer, just like in the movie Star Wars: Episode I – The Phantom Menace . This article details the multiplayer protocol and a vulnerability allowing remote code execution.
By synacktiv.com via hugoarnal · synacktiv.com
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.