GHSA-p6j8-hgv5-m35g
HIGHGHSA-p6j8-hgv5-m35g is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.jboss.remoting:jboss-remoting. O3 Security confirms whether GHSA-p6j8-hgv5-m35g is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Uncontrolled Resource Consumption in jboss-remoting
Blast Radius
org.jboss.remoting:jboss-remotingReal-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
A flaw was found in jboss-remoting in versions before 5.0.20.SP1-redhat-00001. A malicious attacker could cause threads to hold up forever in the EJB server by writing a sequence of bytes corresponding to the expected messages of a successful EJB client request, but omitting the ACK messages, or just tamper with jboss-remoting code, deleting the lines that send the ACK message from the EJB client code resulting in a denial of service. The highest threat from this vulnerability is to system availability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jboss.remoting:jboss-remoting | all versions | 5.0.20.Final |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jboss.remoting:jboss-remoting. 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 org.jboss.remoting:jboss-remoting to 5.0.20.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p6j8-hgv5-m35g 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-p6j8-hgv5-m35g 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-p6j8-hgv5-m35g. 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-p6j8-hgv5-m35g in your dependencies?
O3 detects GHSA-p6j8-hgv5-m35g across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.