Memory Corruption in Mooncake Transfer Engine

Executive Summary

This vulnerability is an unauthenticated arbitrary memory read/write issue in the Mooncake transfer engine before version 0.3.13. It stems from an untrusted pointer dereference in ServerSession::readHeader that allows attackers to send crafted SessionHeader packets with arbitrary memory addresses and sizes using READ or WRITE opcodes via the TCP transport data port. This can lead to disclosure of sensitive data like KV cache contents, prompts, and secrets, or memory corruption that may result in arbitrary code execution.

Useful 0 Not Useful 0

Detection Guidance

Check if Mooncake transfer engine version is below 0.3.13 by running: mooncake-transfer-engine --version. Scan for open TCP ports in the 15000-17000 range using netstat -tulnp | grep -E '15000|16000|17000'. Monitor for unauthorized memory access attempts in logs or use network traffic analysis tools like tcpdump to inspect malformed SessionHeader packets.

Useful 0 Not Useful 0

Impact Analysis

If you use Mooncake transfer engine versions before 0.3.13, attackers on the same network can exploit this flaw to read or write arbitrary memory in the engine process. This could allow them to steal sensitive data such as prompts, secrets, or KV cache contents, corrupt memory to cause crashes or execute malicious code, and potentially gain control over the system hosting the Mooncake service.

Useful 0 Not Useful 0

Compliance Impact

This vulnerability could lead to unauthorized access and exposure of sensitive data such as personally identifiable information (PII) or protected health information (PHI), which are covered under regulations like GDPR and HIPAA. A successful exploit may result in data breaches, violating compliance requirements for data confidentiality and security, potentially leading to legal penalties, reputational damage, and loss of trust.

Useful 0 Not Useful 0

Mitigation Strategies

Upgrade Mooncake transfer engine to version 0.3.13 or later immediately. If upgrading is not possible, disable the TCP transport data port or restrict access via firewall rules to trusted IPs only. Ensure no sensitive data is exposed on the vulnerable port by reviewing network configurations.

Useful 0 Not Useful 0