What is GHSA-W98G-5FMX-WM4X?

GHSA-W98G-5FMX-WM4X is a medium-severity uncontrolled resource consumption vulnerability in pocketmine/raklib (composer), affecting versions >= 0.14.0, < 0.14.6. It is fixed in 0.14.6, 0.15.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is GHSA-W98G-5FMX-WM4X?

GHSA-W98G-5FMX-WM4X has a CVSS score of 5.3 (Medium). 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/raklib are affected by GHSA-W98G-5FMX-WM4X?

pocketmine/raklib (composer) versions >= 0.14.0, < 0.14.6 is affected.

Is there a fix for GHSA-W98G-5FMX-WM4X?

Yes. GHSA-W98G-5FMX-WM4X is fixed in 0.14.6, 0.15.1. Upgrade to this version or later.

Is GHSA-W98G-5FMX-WM4X exploitable, and should I be worried?

Whether GHSA-W98G-5FMX-WM4X 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.

What actually determines whether GHSA-W98G-5FMX-WM4X 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-W98G-5FMX-WM4X?

Upgrade: pocketmine/raklib to 0.14.6 or later, pocketmine/raklib to 0.15.1 or later.

GHSA-W98G-5FMX-WM4X in pocketmine/raklib

Q: How severe is GHSA-W98G-5FMX-WM4X?

GHSA-W98G-5FMX-WM4X has a CVSS score of 5.3 (Medium). 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.

Q: Which versions of pocketmine/raklib are affected by GHSA-W98G-5FMX-WM4X?

pocketmine/raklib (composer) versions >= 0.14.0, < 0.14.6 is affected.

Q: Is there a fix for GHSA-W98G-5FMX-WM4X?

Yes. GHSA-W98G-5FMX-WM4X is fixed in 0.14.6, 0.15.1. Upgrade to this version or later.

Q: Is GHSA-W98G-5FMX-WM4X exploitable, and should I be worried?

Whether GHSA-W98G-5FMX-WM4X 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.

Q: What actually determines whether GHSA-W98G-5FMX-WM4X 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.

Q: How do I fix GHSA-W98G-5FMX-WM4X?

Upgrade: pocketmine/raklib to 0.14.6 or later, pocketmine/raklib to 0.15.1 or later.

Summary

pocketmine/raklib reliable-ordered queue size is unlimited, allowing a session to hog server memory

Workarounds

No workaround is known.

Impact

A client can send reliable-ordered packets 0, 2, 3, 4, 5 ... etc, and all the packets 2 and up will stay in the reliable-ordered queue until 1 arrives. A malicious client can exploit this to waste all available server memory by simply never sending the missing packet. Since the server doesn't make any effort to limit the size of the queue or detect this kind of abuse, this problem is easy to abuse.

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

GHSA-W98G-5FMX-WM4X has a CVSS score of 5.3 (Medium). 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 (0.14.6, 0.15.1); upgrading removes the vulnerable code path.

Affected versions

pocketmine/raklib (>= 0.14.0, < 0.14.6) pocketmine/raklib (>= 0.15.0, < 0.15.1)

Security releases

pocketmine/raklib → 0.14.6 (composer) pocketmine/raklib → 0.15.1 (composer)

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 environment New to Kodem? Get a demo →

Remediation advice

This bug was fixed on the 0.14.x and 0.15.x release lines by 371190f5854372154d1b263cd2a10e658e92bebe.

Frequently Asked Questions

What is GHSA-W98G-5FMX-WM4X? GHSA-W98G-5FMX-WM4X is a medium-severity uncontrolled resource consumption vulnerability in pocketmine/raklib (composer), affecting versions >= 0.14.0, < 0.14.6. It is fixed in 0.14.6, 0.15.1. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is GHSA-W98G-5FMX-WM4X? GHSA-W98G-5FMX-WM4X has a CVSS score of 5.3 (Medium). 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/raklib are affected by GHSA-W98G-5FMX-WM4X? pocketmine/raklib (composer) versions >= 0.14.0, < 0.14.6 is affected.
Is there a fix for GHSA-W98G-5FMX-WM4X? Yes. GHSA-W98G-5FMX-WM4X is fixed in 0.14.6, 0.15.1. Upgrade to this version or later.
Is GHSA-W98G-5FMX-WM4X exploitable, and should I be worried? Whether GHSA-W98G-5FMX-WM4X 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-W98G-5FMX-WM4X 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-W98G-5FMX-WM4X?
- Upgrade pocketmine/raklib to 0.14.6 or later
- Upgrade pocketmine/raklib to 0.15.1 or later