Security readout for executives and security teams
Plain-English summary
CVE-2020-35510 is an availability flaw in jboss-remoting. An attacker could make EJB server threads wait indefinitely by causing expected request traffic to miss acknowledgement messages. The public bundle does not provide CVSS scoring or evidence of active exploitation.
Executive priority
Treat as a service availability risk for affected Java/EJB environments. Prioritize remediation where EJB remoting is reachable beyond trusted application tiers or supports business-critical services.
Technical view
The flaw is classified as CWE-400 resource consumption. The source describes jboss-remoting versions before 5.0.20.SP1-redhat-00001, where missing ACK handling in EJB client request flows can leave server threads held forever, causing denial of service.
Likely exposure
Exposure is likely limited to environments running jboss-remoting with EJB server communication paths reachable by untrusted or semi-trusted clients. The bundle does not identify specific distributions, internet exposure patterns, or affected CPEs.
Exploitation context
The source describes a denial-of-service condition requiring crafted or tampered EJB client message behavior. KEV is false, and the provided sources do not state known exploitation in the wild.
Researcher notes
Evidence is sparse: no CVSS vector, no CPEs, and only one referenced Red Hat Bugzilla link in the bundle. Analysis should stay anchored to jboss-remoting and EJB availability impact until vendor-specific advisories are confirmed.
Mitigation direction
- Inventory systems and applications using jboss-remoting.
- Check whether deployed versions are before 5.0.20.SP1-redhat-00001.
- Upgrade to 5.0.20.SP1-redhat-00001 or later where vendor guidance confirms applicability.
- Restrict EJB/remoting access to trusted networks and clients.
- Monitor EJB server thread exhaustion and unexplained availability degradation.
Validation and detection
- Confirm jboss-remoting package or library versions in deployed applications.
- Map which services expose EJB remoting paths to clients.
- Review vendor advisories for platform-specific fixed builds.
- Check monitoring for stuck server threads or resource exhaustion symptoms.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-400: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2020-35510 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://bugzilla.redhat.com/show_bug.cgi?id=1905796CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.