The org.jboss.remoting.transport.bisocket.BisocketServerInvoker$SecondaryServerSocketThread.run method in JBoss Remoting 2.2.x before 2.2.3.
The org.jboss.remoting.transport.bisocket.BisocketServerInvoker$SecondaryServerSocketThread.run method in JBoss Remoting 2.2.x before 2.2.3.SP4 and 2.5.x before 2.5.3.SP2 in Red Hat JBoss Enterprise Application Platform (aka JBoss EAP or JBEAP) 4.3 through 4.3.0.CP09, and 5.1.0; and JBoss Enterprise Web Platform (aka JBEWP) 5.1.0; allows remote attackers to cause a denial of service (daemon outage) by establishing a bisocket control connection TCP session, and then not sending any application data.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for help- Published
- Dec 30, 2010
- Updated
- Jun 16, 2026
- EPSS
- 2.6% · 85th percentile
- CWE
- CWE-20
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
11
Monitor
Low priority for now.
- CVSS
- 10 / 40 · 2.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.6%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| redhat | jboss remoting | cpe:2.3:a:redhat:jboss_remoting |
| redhat | jboss enterprise application platform | cpe:2.3:a:redhat:jboss_enterprise_application_platform |
| redhat | jboss enterprise web platform | cpe:2.3:a:redhat:jboss_enterprise_web_platform |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- redhat jboss enterprise application platform4.3.0
- redhat jboss enterprise application platform5.1.0
- redhat jboss enterprise web platform5.1.0
- redhat jboss remoting2.2.0
- redhat jboss remoting2.2.2
- redhat jboss remoting2.2.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | glassfish-jaxb | before 0:2.1.4-1.17.patch04.ep1.el4 | 0:2.1.4-1.17.patch04.ep1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | glassfish-jaxws | before 0:2.1.1-1jpp.ep1.13.el4 | 0:2.1.1-1jpp.ep1.13.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | hibernate3 | before 1:3.2.4-1.SP1_CP11.0jpp.ep2.0.el4 | 1:3.2.4-1.SP1_CP11.0jpp.ep2.0.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | hibernate3-annotations | before 0:3.3.1-2.0.GA_CP04.ep1.el4 | 0:3.3.1-2.0.GA_CP04.ep1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | hibernate3-annotations-javadoc | before 0:3.3.1-2.0.GA_CP04.ep1.el4 | 0:3.3.1-2.0.GA_CP04.ep1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | hibernate3-javadoc | before 1:3.2.4-1.SP1_CP11.0jpp.ep2.0.el4 | 1:3.2.4-1.SP1_CP11.0jpp.ep2.0.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | javassist | before 0:3.9.0-2.ep1.1.el4 | 0:3.9.0-2.ep1.1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jboss-common | before 0:1.2.2-1.ep1.1.el4 | 0:1.2.2-1.ep1.1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jboss-messaging | before 0:1.4.0-4.SP3_CP11.1.ep1.el4 | 0:1.4.0-4.SP3_CP11.1.ep1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jboss-remoting | before 0:2.2.3-4.SP3.ep1.el4 | 0:2.2.3-4.SP3.ep1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jboss-seam | before 0:1.2.1-3.JBPAPP_4_3_0_GA.ep1.22.el4 | 0:1.2.1-3.JBPAPP_4_3_0_GA.ep1.22.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jboss-seam-docs | before 0:1.2.1-3.JBPAPP_4_3_0_GA.ep1.22.el4 | 0:1.2.1-3.JBPAPP_4_3_0_GA.ep1.22.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jboss-seam2 | before 0:2.0.2.FP-1.ep1.26.el4 | 0:2.0.2.FP-1.ep1.26.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jboss-seam2-docs | before 0:2.0.2.FP-1.ep1.26.el4 | 0:2.0.2.FP-1.ep1.26.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jbossas | before 0:4.3.0-8.GA_CP09.2.ep1.el4 | 0:4.3.0-8.GA_CP09.2.ep1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jbossas-4.3.0.GA_CP09-bin | before 0:4.3.0-8.GA_CP09.2.ep1.el4 | 0:4.3.0-8.GA_CP09.2.ep1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jbossas-client | before 0:4.3.0-8.GA_CP09.2.ep1.el4 | 0:4.3.0-8.GA_CP09.2.ep1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jbossts | before 1:4.2.3-2.SP5_CP10.1jpp.ep1.1.el4 | 1:4.2.3-2.SP5_CP10.1jpp.ep1.1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jbossweb | before 0:2.0.0-7.CP15.0jpp.ep1.1.el4 | 0:2.0.0-7.CP15.0jpp.ep1.1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jbossws | before 0:2.0.1-6.SP2_CP09.2.ep1.el4 | 0:2.0.1-6.SP2_CP09.2.ep1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jbossws-common | before 0:1.0.0-3.GA_CP06.1.ep1.el4 | 0:1.0.0-3.GA_CP06.1.ep1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | jgroups | before 1:2.4.9-1.ep1.el4 | 1:2.4.9-1.ep1.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | rh-eap-docs | before 0:4.3.0-8.GA_CP09.ep1.3.el4 | 0:4.3.0-8.GA_CP09.ep1.3.el4 |
| Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | rh-eap-docs-examples | before 0:4.3.0-8.GA_CP09.ep1.3.el4 | 0:4.3.0-8.GA_CP09.ep1.3.el4 |
+35
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2010-4265The org.jboss.remoting.transport.bisocket.BisocketServerInvoker$SecondaryServerSocketThread.run method in JBoss Remoting 2.2.x before 2.2.3.11Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| red hat:glassfish-jaxb | 0:2.1.4-1.17.patch04.ep1.el4 · Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | Package registry (OSV) |
| red hat:glassfish-jaxws | 0:2.1.1-1jpp.ep1.13.el4 · Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | Package registry (OSV) |
| red hat:hibernate3 | 1:3.2.4-1.SP1_CP11.0jpp.ep2.0.el4 · Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | Package registry (OSV) |
| red hat:hibernate3-annotations | 0:3.3.1-2.0.GA_CP04.ep1.el4 · Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | Package registry (OSV) |
| red hat:hibernate3-annotations-javadoc | 0:3.3.1-2.0.GA_CP04.ep1.el4 · Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | Package registry (OSV) |
| red hat:hibernate3-javadoc | 1:3.2.4-1.SP1_CP11.0jpp.ep2.0.el4 · Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | Package registry (OSV) |
| red hat:javassist | 0:3.9.0-2.ep1.1.el4 · Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | Package registry (OSV) |
| red hat:jboss-common | 0:1.2.2-1.ep1.1.el4 · Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | Package registry (OSV) |
| red hat:jboss-messaging | 0:1.4.0-4.SP3_CP11.1.ep1.el4 · Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | Package registry (OSV) |
| red hat:jboss-remoting | 0:2.2.3-4.SP3.ep1.el4 · Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | Package registry (OSV) |
| red hat:jboss-seam | 0:1.2.1-3.JBPAPP_4_3_0_GA.ep1.22.el4 · Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | Package registry (OSV) |
| red hat:jboss-seam-docs | 0:1.2.1-3.JBPAPP_4_3_0_GA.ep1.22.el4 · Red Hat:jboss_enterprise_application_platform:4.3.0::el4 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- High
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
AV:N/AC:H/Au:N/C:N/I:N/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- securitytracker.com/id?1024813
- www.redhat.com/support/errata/RHSA-2010-0937.html
- www.redhat.com/support/errata/RHSA-2010-0938.html
- www.redhat.com/support/errata/RHSA-2010-0939.html
- www.redhat.com/support/errata/RHSA-2010-0959.html
- www.redhat.com/support/errata/RHSA-2010-0960.html
- www.redhat.com/support/errata/RHSA-2010-0961.html
- www.redhat.com/support/errata/RHSA-2010-0962.html
- www.redhat.com/support/errata/RHSA-2010-0963.html
- bugzilla.redhat.com/show_bug.cgi?id=641389
- issues.jboss.org/browse/JBPAPP-5253
- issues.jboss.org/browse/JBREM-1261
Vendor advisories and official records. Exploit/PoC links are deliberately left out.