Summary
Improperly checked metadata on tools/armour itemstacks received from the client
Workarounds
In theory this can be checked by plugins using a custom TypeConverter, but this is likely to be very cumbersome.
For more information
- Email us at [email protected]
Impact
Due to a workaround applied in 1.13, an attacker may send a negative damage/meta value in a tool or armour item's NBT, which TypeConverter then blindly uses as if it was valid without being checked.
When this invalid metadata value reaches Durable->setDamage(), an exception is thrown because the metadata is not within the expected range for damage values.
This can be reproduced with either a too-large damage value, or a negative one.
GHSA-46C5-PFJ8-FV65 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.2.4); upgrading removes the vulnerable code path.
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
c8e1cfcbee4945fd4b63d2a7e96025c59744d4f1
Frequently Asked Questions
- What is GHSA-46C5-PFJ8-FV65? GHSA-46C5-PFJ8-FV65 is a high-severity security vulnerability in pocketmine/pocketmine-mp (composer), affecting versions < 4.2.4. It is fixed in 4.2.4.
- How severe is GHSA-46C5-PFJ8-FV65? GHSA-46C5-PFJ8-FV65 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.
- Which versions of pocketmine/pocketmine-mp are affected by GHSA-46C5-PFJ8-FV65? pocketmine/pocketmine-mp (composer) versions < 4.2.4 is affected.
- Is there a fix for GHSA-46C5-PFJ8-FV65? Yes. GHSA-46C5-PFJ8-FV65 is fixed in 4.2.4. Upgrade to this version or later.
- Is GHSA-46C5-PFJ8-FV65 exploitable, and should I be worried? Whether GHSA-46C5-PFJ8-FV65 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-46C5-PFJ8-FV65 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-46C5-PFJ8-FV65? Upgrade
pocketmine/pocketmine-mpto 4.2.4 or later.