NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Uncontrolled Resource Consumption in jboss-remotingGHSA-p6j8-hgv5-m35g

HIGH

GHSA-p6j8-hgv5-m35g is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in org.jboss.remoting:jboss-remoting. A fix is available for org.jboss.remoting:jboss-remoting — see the affected versions and patch details below.

Also known asCVE-2020-35510
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk
0.06%0.57%1.08%1.59%0.6%1.1%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
☕org.jboss.remoting:jboss-remoting

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 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

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jboss.remoting:jboss-remotingall versions5.0.20.Finalorg.jboss.remoting:jboss-remoting:5.0.20.Final

Affected Products

1 product · 2 configurations
Application
jboss-remotingredhat
< 5.0.20
1 version
5.0.20

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jboss.remoting:jboss-remoting, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. 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.

  3. Workarounds

    Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate
ProductFixed inAdvisory
Red Hat EAP-XP via EAP 7.3.x basejboss-remotingRHSA-2021:2210
Red Hat Fuse 7.10jboss-remotingRHSA-2021:5134
Red Hat JBoss Enterprise Application Platform 7jboss-remotingRHSA-2021:0885
Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 6eap7-activemq-artemis-0:2.9.0-9.redhat_00019.1.el6eapRHSA-2021:0872
Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 7eap7-activemq-artemis-0:2.9.0-9.redhat_00019.1.el7eapRHSA-2021:0873
Red Hat JBoss Enterprise Application Platform 7.3 for RHEL 8eap7-activemq-artemis-0:2.9.0-9.redhat_00019.1.el8eapRHSA-2021:0874
Red Hat Single Sign-On 7.4.6jboss-remotingRHSA-2021:0974

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-p6j8-hgv5-m35g in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Uncontrolled Resource Consumption in jboss-remoting