Summary
Buffer length underflow in LoginPacket causing unchecked exceptions to be thrown
Workarounds
This can be worked around by registering a custom LoginPacket implementation into PacketPool which overrides this code to patch it.
For more information
- Email us at [email protected]
Impact
LoginPacket uses BinaryStream->getLInt() to read the lengths of JSON payloads it wants to decode. Unfortunately, BinaryStream->getLInt() returns a signed integer, meaning that a malicious client can craft a packet with a large uint32 value for payload buffer size (which would be interpreted as a negative signed int32), causing BinaryStream->get() to throw an exception.
In the context of PocketMine-MP, this leads to a server crash when the vulnerability is exploited.
GHSA-5JFW-35XP-5M42 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 (8.0.2); 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
e3fce7632b94e83fd6a518a87dcaf6a11681c4ac
Frequently Asked Questions
- What is GHSA-5JFW-35XP-5M42? GHSA-5JFW-35XP-5M42 is a high-severity security vulnerability in pocketmine/bedrock-protocol (composer), affecting versions < 8.0.2. It is fixed in 8.0.2.
- How severe is GHSA-5JFW-35XP-5M42? GHSA-5JFW-35XP-5M42 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/bedrock-protocol are affected by GHSA-5JFW-35XP-5M42? pocketmine/bedrock-protocol (composer) versions < 8.0.2 is affected.
- Is there a fix for GHSA-5JFW-35XP-5M42? Yes. GHSA-5JFW-35XP-5M42 is fixed in 8.0.2. Upgrade to this version or later.
- Is GHSA-5JFW-35XP-5M42 exploitable, and should I be worried? Whether GHSA-5JFW-35XP-5M42 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-5JFW-35XP-5M42 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-5JFW-35XP-5M42? Upgrade
pocketmine/bedrock-protocolto 8.0.2 or later.