What is CVE-2020-35510?

CVE-2020-35510 is a high-severity uncontrolled resource consumption vulnerability in org.jboss.remoting:jboss-remoting (maven), affecting versions <= 5.0.19.Final. It is fixed in 5.0.20.Final. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

How severe is CVE-2020-35510?

CVE-2020-35510 has a CVSS score of 7.5 (High). 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 org.jboss.remoting:jboss-remoting are affected by CVE-2020-35510?

org.jboss.remoting:jboss-remoting (maven) versions <= 5.0.19.Final is affected.

Is there a fix for CVE-2020-35510?

Yes. CVE-2020-35510 is fixed in 5.0.20.Final. Upgrade to this version or later.

Is CVE-2020-35510 exploitable, and should I be worried?

Whether CVE-2020-35510 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.

What actually determines whether CVE-2020-35510 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.

CVE-2020-35510 in org.jboss.remoting:jboss-remoting

Q: How severe is CVE-2020-35510?

CVE-2020-35510 has a CVSS score of 7.5 (High). 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.

Q: Which versions of org.jboss.remoting:jboss-remoting are affected by CVE-2020-35510?

org.jboss.remoting:jboss-remoting (maven) versions <= 5.0.19.Final is affected.

Q: Is there a fix for CVE-2020-35510?

Yes. CVE-2020-35510 is fixed in 5.0.20.Final. Upgrade to this version or later.

Q: Is CVE-2020-35510 exploitable, and should I be worried?

Whether CVE-2020-35510 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.

Q: What actually determines whether CVE-2020-35510 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.

Q: How do I fix CVE-2020-35510?

Upgrade org.jboss.remoting:jboss-remoting to 5.0.20.Final or later.

Summary

Uncontrolled Resource Consumption in jboss-remoting

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.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

CVE-2020-35510 has a CVSS score of 7.5 (High). The vector is network-reachable, no 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 (5.0.20.Final); upgrading removes the vulnerable code path.

Affected versions

org.jboss.remoting:jboss-remoting (<= 5.0.19.Final)

Security releases

org.jboss.remoting:jboss-remoting → 5.0.20.Final (maven)

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 environment New to Kodem? Get a demo →

Remediation advice

Upgrade org.jboss.remoting:jboss-remoting to 5.0.20.Final or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2020-35510? CVE-2020-35510 is a high-severity uncontrolled resource consumption vulnerability in org.jboss.remoting:jboss-remoting (maven), affecting versions <= 5.0.19.Final. It is fixed in 5.0.20.Final. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
How severe is CVE-2020-35510? CVE-2020-35510 has a CVSS score of 7.5 (High). 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 org.jboss.remoting:jboss-remoting are affected by CVE-2020-35510? org.jboss.remoting:jboss-remoting (maven) versions <= 5.0.19.Final is affected.
Is there a fix for CVE-2020-35510? Yes. CVE-2020-35510 is fixed in 5.0.20.Final. Upgrade to this version or later.
Is CVE-2020-35510 exploitable, and should I be worried? Whether CVE-2020-35510 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 CVE-2020-35510 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 CVE-2020-35510? Upgrade org.jboss.remoting:jboss-remoting to 5.0.20.Final or later.