Quick answers
- Is CVE-2022-51013 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2022-51013 being exploited in the wild.
- How severe is CVE-2022-51013?
- Medium severity, with a CVSS score of 6.5, published 7 September 2026.
- Which products and versions are affected?
- pocketmine/pocketmine-mp (Packagist) ECOSYSTEM:introduced=0,fixed=4.2.4.
- Is there a fix for CVE-2022-51013?
- Yes. pocketmine/pocketmine-mp (Packagist): upgrade to 4.2.4 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2022-51013 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2022-51013?
- Check whether you run pocketmine/pocketmine-mp (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- pocketmine/pocketmine-mp (Packagist): upgrade to 4.2.4 or later
composer require pocketmine/pocketmine-mp:^4.2.4
Technical details
PocketMine-MP versions before 4.2.3 fail to validate damage metadata values in tool and armor item NBT data received from clients. The vulnerability exists in the TypeConverter class, which blindly uses metadata values from client-sent itemstack NBT without range checking. When an attacker sends negative or out-of-range damage values (outside 0-0x7fff), the Durable class throws an unhandled exception, crashing the server. The attack requires network access and low privileges (ability to send game packets), with no user interaction needed. Patch version 4.2.4 adds explicit range validation in TypeConverter before processing the metadata.
Affected products
- PocketMine PocketMine-MP before 4.2.3
Identifiers
- CVE-2022-51013
- GHSA-46c5-pfj8-fv65
Timeline
- 2022-03-18: disclosed
- 2022: patched: patch version 4.2.4 released