GHSA-whj9-m24x-qhhp
MEDIUMFastAsyncWorldEdit vulnerable to Uncontrolled Resource Consumption
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
com.fastasyncworldedit:FastAsyncWorldEdit-Core☕com.fastasyncworldedit:FastAsyncWorldEdit-BukkitReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Coordinated Disclosure Timeline
- 10.06.2023: Issue reported to IntellectualSites
- 11.06.2023: Issue is acknowledged
- 12.06.2023: Issue has been fixed
- 22.06.2023: Advisory has been published
Impacted version range
Before 2.6.3
Details
Proof of Concept
As a user, do the following:
- Select position 1 via
//pos1 - Select position 2 adding the "Infinity" keyword via
//pos2 Infinity - Execute any further operation.
The steps 1 and 2 are interchangeable.
Impact
Such a task has a possibility of bringing the performing server down.
CVE
- CVE-2023-35925
Credit
This issue was discovered and reported by @SuperMonis.
Solution
On June 12, 2023, a patch, https://github.com/IntellectualSites/FastAsyncWorldEdit/pull/2285, has been merged addressing the vulnerability. We strongly recommend users to update their version of FastAsyncWorldEdit to 2.6.3 as soon as possible.
Workarounds
There is no direct mitigation besides updating FastAsyncWorldEdit to a patched version.
Additional Information
Users with access to the logs/ folder or shell access on their server can try to identify possible abuses of this issue by going through the logs.
To sieve through the data, you can use the regex query \/\/pos[12] Infinity, then investigate all log entries that return results.
Disclosure Policy
If you discover a security vulnerability within our software, please report the issue according to our vulnerability disclosure policy.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.fastasyncworldedit:FastAsyncWorldEdit-Core | all versions | 2.6.3 |
| ☕Maven | com.fastasyncworldedit:FastAsyncWorldEdit-Bukkit | all versions | 2.6.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.fastasyncworldedit:FastAsyncWorldEdit-Core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update com.fastasyncworldedit:FastAsyncWorldEdit-Core to 2.6.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-whj9-m24x-qhhp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-whj9-m24x-qhhp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-whj9-m24x-qhhp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-whj9-m24x-qhhp in your dependencies?
O3 detects GHSA-whj9-m24x-qhhp across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.