Summary
Inability to de-op players if listed in ops.txt with non-lowercase letters
Workarounds
This can be easily addressed by removing the offending lines from ops.txt manually.
For more information
If you have any questions or comments about this advisory:
- Open an issue in pmmp/PocketMine-MP
- Email us at [email protected]
Impact
Originally reported in iTXTech/Genisys#1188
PotterHarry98
potterharry98
deop PotterHarry98
will remove potterharry98 from the ops.txt but not PotterHarry98.
Operator permissions are checked using Config->exists() with lowercase=true, which will result in a match:
https://github.com/pmmp/PocketMine-MP/blob/22bb1ce8e03dba57173debf0415390511d68e045/src/utils/Config.php#L449
This means that it's possible to make yourself impossible to de-op (using commands) by adding your name to ops.txt with uppercase letters.
GHSA-J5QG-W9JG-3WG3 has a CVSS score of 3.3 (Low). The vector is requires local access, low 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.0.3); 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
4d37b79ff7f9d9452e988387f97919a9a1c4954e
Frequently Asked Questions
- What is GHSA-J5QG-W9JG-3WG3? GHSA-J5QG-W9JG-3WG3 is a low-severity security vulnerability in pocketmine/pocketmine-mp (composer), affecting versions < 4.0.3. It is fixed in 4.0.3.
- How severe is GHSA-J5QG-W9JG-3WG3? GHSA-J5QG-W9JG-3WG3 has a CVSS score of 3.3 (Low). 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-J5QG-W9JG-3WG3? pocketmine/pocketmine-mp (composer) versions < 4.0.3 is affected.
- Is there a fix for GHSA-J5QG-W9JG-3WG3? Yes. GHSA-J5QG-W9JG-3WG3 is fixed in 4.0.3. Upgrade to this version or later.
- Is GHSA-J5QG-W9JG-3WG3 exploitable, and should I be worried? Whether GHSA-J5QG-W9JG-3WG3 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-J5QG-W9JG-3WG3 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-J5QG-W9JG-3WG3? Upgrade
pocketmine/pocketmine-mpto 4.0.3 or later.