How severe is GHSA-qcch-9268-59jw?

GHSA-qcch-9268-59jw has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-qcch-9268-59jw?

GHSA-qcch-9268-59jw affects the following packages: org.jboss:jboss-ejb-client (Maven). Ecosystems affected: Maven.

How do I fix GHSA-qcch-9268-59jw?

Update org.jboss:jboss-ejb-client to 4.0.34.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qcch-9268-59jw is resolved across your whole dependency graph.

How do I detect GHSA-qcch-9268-59jw in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jboss:jboss-ejb-client. 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.

How do I mitigate GHSA-qcch-9268-59jw if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-qcch-9268-59jw?

O3 pinpoints whether GHSA-qcch-9268-59jw is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-qcch-9268-59jw actively exploited in the wild?

No public exploit code has been indexed for GHSA-qcch-9268-59jw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-qcch-9268-59jw?

GHSA-qcch-9268-59jw has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 64th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-qcch-9268-59jw?

GHSA-qcch-9268-59jw is classified as Uncontrolled Resource Consumption (CWE-400). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qcch-9268-59jw published, and has it been updated?

GHSA-qcch-9268-59jw was published on May 24, 2022 and was last updated on March 10, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-qcch-9268-59jw: Wildfly EJB Client causes DoS (Medium 6.5)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk64th percentile+0.95%

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

1 pkg affected

☕org.jboss:jboss-ejb-client

Real-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 discovered in Wildfly's EJB Client as shipped with Red Hat JBoss EAP 7, where some specific EJB transaction objects may get accumulated over the time and can cause services to slow down and eventually unavailable. An attacker can take advantage and cause denial of service attack and make services unavailable.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jboss:jboss-ejb-client`	all versions	4.0.34.Final

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jboss:jboss-ejb-client. 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:jboss-ejb-client to 4.0.34.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qcch-9268-59jw 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-qcch-9268-59jw 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-qcch-9268-59jw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

A flaw was discovered in Wildfly's EJB Client as shipped with Red Hat JBoss EAP 7, where some specific EJB transaction objects may get accumulated over the time and can cause services to slow down and eventually unavailable. An attacker can take advantage and cause denial of service attack and make services unavailable.

O3 Security · Impact-Aware SCA

Is GHSA-qcch-9268-59jw in your dependencies?

O3 detects GHSA-qcch-9268-59jw across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-qcch-9268-59jw