ELSEIF
Your brief EB
545 stories from 214 feeds 1272 clusters Refreshed 6 minutes ago next pull 22:40

SECURITY Signal 56

MECCHA CHAMELEON patched delayed RCE via malicious custom maps writing arbitrary files

A security researcher found a remote code execution vulnerability in MECCHA CHAMELEON where malicious custom maps could write files to arbitrary system locations and execute code after restart

WHY IT MATTERS

This vulnerability exposed players to arbitrary file writes and delayed remote code execution simply by joining a multiplayer lobby. The attack surface was significant given the game's reliance on community-created content and automatic map downloads. The patch demonstrates how exposed Blueprint functions in Unreal Engine can create unexpected security risks in multiplayer games

Written by elseif from the cluster below · every claim links back to a source

The three things worth knowing

01

Malicious custom maps could write files to arbitrary system locations using an exposed Unreal Engine Blueprint function

02

The vulnerability enabled delayed remote code execution after system restart by writing to startup directories

03

The issue was patched in version 4.0.0 with automatic updates before game launch

THE READ

What the cluster adds up to.

ORIGINAL ANALYSIS

The vulnerability demonstrates how game modding systems can create unexpected attack surfaces. MECCHA CHAMELEON's implementation of Unreal Engine Blueprints allowed community-created maps to execute code with the same permissions as the game client. This differs from traditional game maps that only contain level geometry and assets, as Blueprints enable actual program logic to be distributed through map files.

The specific attack vector exploited the 'Finish Recording Output' function exposed to Blueprints. This function's ability to write audio files to arbitrary paths - including absolute paths and relative paths traversing directories - created the file write primitive. The security impact was amplified by the game's automatic map download system, which forced players to load untrusted content when joining multiplayer lobbies.

The delayed execution aspect of this vulnerability made it particularly dangerous. By writing executables to startup directories, attackers could maintain persistence across system reboots. This attack pattern bypasses some traditional security controls that focus on immediate code execution, as the malicious payload would only activate after the game session ended and the system restarted.

The patching approach highlights the challenges of securing modding ecosystems. While the specific vulnerability was fixed, the underlying architecture of exposing Blueprint functions to community content remains. Game developers must carefully audit which engine functions are exposed to modding systems, particularly those that interact with the filesystem or operating system. The automatic update mechanism helps ensure players receive fixes, but doesn't address the fundamental design considerations for moddable games.

Written by elseif from the cluster below · checked for specifics the sources never contained

THE CLUSTER

Same story, 1 feed.

ORDERED BY FIRST SEEN
Aikido Security's Blog MECCHA CHAMELEON can't hide from the RCE Open ↗