Summary
PocketMine-MP has potential memory/network vulnerability from repeated ResourcePackClientResponsePacket packets
During the resource pack stage of logging in, after the server sends ResourcePackStackPacket, a malicious client can send a batch of multiple ResourcePackClientResponsePacket packets with status ResourcePackClientResponsePacket::STATUS_COMPLETED causing the server to repeatedly execute pre-spawn progression.
Workarounds
Plugins can use their own PacketHandler classes that reject/ignore any extra ResourcePackClientResponsePacket packets.
Impact
Multiple Player objects can be created for just a single session, increasing memory usage and amplifying outbound network traffic from duplication of large pre-spawn packets such as AvailableCommandsPacket and CreativeContentPacket.
Affected versions
Security releases
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 issue was patched in https://github.com/pmmp/PocketMine-MP/commit/7a27894146a04964ab628ed9033140fdbf887ff3 and released in 5.44.2.
Frequently Asked Questions
- What is GHSA-PG53-P7QP-65CV? GHSA-PG53-P7QP-65CV is a low-severity security vulnerability in pocketmine/pocketmine-mp (composer), affecting versions < 5.44.2. It is fixed in 5.44.2.
- Which versions of pocketmine/pocketmine-mp are affected by GHSA-PG53-P7QP-65CV? pocketmine/pocketmine-mp (composer) versions < 5.44.2 is affected.
- Is there a fix for GHSA-PG53-P7QP-65CV? Yes. GHSA-PG53-P7QP-65CV is fixed in 5.44.2. Upgrade to this version or later.
- Is GHSA-PG53-P7QP-65CV exploitable, and should I be worried? Whether GHSA-PG53-P7QP-65CV 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
- What actually determines whether GHSA-PG53-P7QP-65CV 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.
- How do I fix GHSA-PG53-P7QP-65CV? Upgrade
pocketmine/pocketmine-mpto 5.44.2 or later.