GHSA-7WRV-6H42-W54F

GHSA-7WRV-6H42-W54F is a high-severity security vulnerability in pocketmine/pocketmine-mp (composer), affecting versions >= 4.20.0, < 4.22.3. It is fixed in 4.22.3, 5.2.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

PocketMine-MP vulnerable to server crash using badly formatted sign NBT in BlockActorDataPacket

A player sending a packet can cause the server to crash by providing incorrect sign data in NBT in BlockActorDataPacket.

Details

This vulnerability was discovered using the BlockActorDataPacket, but other packets may also be affected. The player would seem to just need to send an NBT with an incorrect type to throw this error.

[Server thread/CRITICAL]: pocketmine\nbt\UnexpectedTagTypeException: "Expected a tag of type pocketmine\nbt\tag\CompoundTag, got pocketmine\nbt\tag\ByteTag" (EXCEPTION) in "pmsrc/vendor/pocketmine/nbt/src/tag/CompoundTag" at line 107
--- Stack trace ---
  #0 pmsrc/src/network/mcpe/handler/InGamePacketHandler(751): pocketmine\nbt\tag\CompoundTag->getCompoundTag(string[9] FrontText)
  #1 pmsrc/vendor/pocketmine/bedrock-protocol/src/BlockActorDataPacket(50): pocketmine\network\mcpe\handler\InGamePacketHandler->handleBlockActorData(object pocketmine\network\mcpe\protocol\BlockActorDataPacket#220241)
  #2 pmsrc/src/network/mcpe/NetworkSession(433): pocketmine\network\mcpe\protocol\BlockActorDataPacket->handle(object pocketmine\network\mcpe\handler\InGamePacketHandler#190572)

PoC

Use a bot or proxy to send a packet when editing a sign. This packet should contain an NBT with incorrect types but correct architecture.

Workarounds

A plugin may be able to handle DataPacketReceiveEvent for BlockActorDataPacket, and verify that the FrontText tag is a TAG_Compound.

Impact

This makes it possible to shutdown a server for someone who knows how to operate it. As this was discovered in 4.22.1, everyone with at least this version is affected.

GHSA-7WRV-6H42-W54F has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.22.3, 5.2.1); upgrading removes the vulnerable code path.

Affected versions

pocketmine/pocketmine-mp (>= 4.20.0, < 4.22.3) pocketmine/pocketmine-mp (>= 5.0.0, < 5.2.1)

Security releases

pocketmine/pocketmine-mp → 4.22.3 (composer) pocketmine/pocketmine-mp → 5.2.1 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

This bug was fixed by 0c250a2ef09627b48aa52302f6cc7e1f2afb70ea in the 4.22.3 and 5.2.1 releases.

Frequently Asked Questions

  1. What is GHSA-7WRV-6H42-W54F? GHSA-7WRV-6H42-W54F is a high-severity security vulnerability in pocketmine/pocketmine-mp (composer), affecting versions >= 4.20.0, < 4.22.3. It is fixed in 4.22.3, 5.2.1.
  2. How severe is GHSA-7WRV-6H42-W54F? GHSA-7WRV-6H42-W54F has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of pocketmine/pocketmine-mp are affected by GHSA-7WRV-6H42-W54F? pocketmine/pocketmine-mp (composer) versions >= 4.20.0, < 4.22.3 is affected.
  4. Is there a fix for GHSA-7WRV-6H42-W54F? Yes. GHSA-7WRV-6H42-W54F is fixed in 4.22.3, 5.2.1. Upgrade to this version or later.
  5. Is GHSA-7WRV-6H42-W54F exploitable, and should I be worried? Whether GHSA-7WRV-6H42-W54F is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether GHSA-7WRV-6H42-W54F is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix GHSA-7WRV-6H42-W54F?
    • Upgrade pocketmine/pocketmine-mp to 4.22.3 or later
    • Upgrade pocketmine/pocketmine-mp to 5.2.1 or later

Other vulnerabilities in pocketmine/pocketmine-mp

Stop the waste.
Protect your environment with Kodem.