LiveActive security incident?Get immediate response
CVE Record

CVE-2010-3862: The org.jboss.remoting.transport.bisocket.BisocketServerInvoker$SecondaryServerSocketThread.run method in J...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is a remote denial-of-service flaw in older JBoss Remoting used by Red Hat JBoss EAP and EWP. An attacker who can reach the bisocket control connection can make the service stop responding by opening a TCP session and withholding application data. It affects availability, not data theft based on the sources. Exposure is most likely in legacy Red Hat JBoss EAP 4.3 through 4.3.0.CP09, EAP 5.1.0, or JBoss EWP 5.1.0 deployments using affected JBoss Remoting bisocket transport. Internet-facing or partner-accessible remoting endpoints raise urgency. Treat this as a targeted availability risk for legacy JBoss environments. It is not presented as data compromise or code execution, but exposed production middleware could suffer service outage. Prioritize remediation where affected JBoss Remoting endpoints support revenue, authentication, or customer-facing services. Mitigation focus: Upgrade JBoss Remoting to 2.2.3.SP4, 2.5.3.SP2, or later vendor-supported packages.; Apply the relevant Red Hat security advisories for the deployed EAP or EWP stream.; Restrict network access to JBoss Remoting bisocket endpoints to trusted systems only..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

cve · low confidence lookup

CVE-2010-3862 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.