CVE-2022-51017

7.5

PocketMine-MP · PocketMine-MP

PocketMine-MP fails to validate the length of skin data fields provided by players, allowing unauthenticated attackers to cause server crashes via oversized input.

Executive summary

A critical input validation vulnerability in PocketMine-MP allows unauthenticated remote attackers to crash game servers, resulting in a complete denial of service.

Vulnerability

This vulnerability is an improper input validation flaw (CWE-20) where the server fails to enforce size limits on skin data fields. An unauthenticated attacker can submit maliciously crafted, oversized data strings that exceed the 32767 byte limit, triggering exceptions during NBT serialization and causing the server process to terminate.

Business impact

The exploitation of this vulnerability results in a denial of service, which disrupts game availability and impacts the user experience. Given the CVSS score of 7.5, this high-severity flaw represents a significant risk to service continuity for server administrators. Frequent crashes may lead to data loss or corruption, depending on the server state at the time of the crash.

Remediation

Immediate Action: Update PocketMine-MP to version 3.26.5, 4.0.5, or any subsequent patched release.

Proactive Monitoring: Monitor server logs for unexpected process terminations or recurring NBT serialization exceptions.

Compensating Controls: While no direct WAF rule can easily parse NBT serialization, network-level rate limiting may help reduce the frequency of malicious payloads arriving at the server.

Exploitation status

Public Exploit Available: Unknown

Analyst recommendation

The risk posed by this vulnerability is significant due to the ease of triggering a crash without requiring authentication. Administrators must prioritize updating to the fixed versions to ensure service stability. Failure to patch leaves the server vulnerable to trivial denial-of-service attacks that can be automated by malicious actors.

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources