Summary
Exploitable inventory component chaining in PocketMine-MP
Workarounds
No practical workarounds are possible, short of backporting the fix or implementing checks in a plugin listening to DataPacketReceiveEvent.
References
c368ebb5e74632bc622534b37cd1447b97281e20
For more information
If you have any questions or comments about this advisory:
- Email us at [email protected]
Impact
Specially crafted InventoryTransactionPackets sent by malicious clients were able to exploit the behaviour of InventoryTransaction->findResultItem() and cause it to take an abnormally long time to execute (causing an apparent server freeze).
The affected code is intended to compact conflicting InventoryActions which are in the same InventoryTransaction by flattening them into a single action. When multiple pathways to a result existed, the complexity of this flattening became exponential.
The problem was fixed by bailing when ambiguities are detected.
At the time of writing, this exploit is being used in the wild by attackers to deny service to servers.
Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.
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
Upgrade to 3.15.4 or newer.
Frequently Asked Questions
- What is GHSA-8JQ6-W5CG-WM45? GHSA-8JQ6-W5CG-WM45 is a high-severity uncontrolled resource consumption vulnerability in pocketmine/pocketmine-mp (composer), affecting versions < 3.15.4. It is fixed in 3.15.4. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
- Which versions of pocketmine/pocketmine-mp are affected by GHSA-8JQ6-W5CG-WM45? pocketmine/pocketmine-mp (composer) versions < 3.15.4 is affected.
- Is there a fix for GHSA-8JQ6-W5CG-WM45? Yes. GHSA-8JQ6-W5CG-WM45 is fixed in 3.15.4. Upgrade to this version or later.
- Is GHSA-8JQ6-W5CG-WM45 exploitable, and should I be worried? Whether GHSA-8JQ6-W5CG-WM45 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-8JQ6-W5CG-WM45 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-8JQ6-W5CG-WM45? Upgrade
pocketmine/pocketmine-mpto 3.15.4 or later.