Security readout for executives and security teams
Plain-English summary
This flaw affects older Red Hat JBoss EAP JMX-Console deployments. The console checked access controls for common request methods only, allowing other methods to bypass the intended gate and reach console handling logic. Although the CVSS score is medium, CISA KEV listing makes exposed legacy systems a business-priority remediation item.
Executive priority
Prioritize remediation for any reachable legacy JBoss EAP instance. KEV status means this is not just theoretical, and administrative-console exposure can create outsized operational risk despite the medium base score.
Technical view
In JBoss EAP 4.2 before 4.2.0.CP09 and 4.3 before 4.3.0.CP08, JMX-Console access control applied only to GET and POST. A remote unauthenticated attacker could use a different HTTP method to invoke the application's GET handler, causing an authorization bypass with limited integrity impact.
Likely exposure
Exposure is most likely in legacy Red Hat JBoss EAP 4.2 or 4.3 systems where the JMX-Console web application remains deployed and reachable. Internet-facing or broadly reachable administrative interfaces carry the highest operational risk.
Exploitation context
CISA KEV indicates known exploitation. The provided bundle does not include exploit prevalence, exploit maturity details, or observed campaign information, so exploitation should be treated as confirmed but not further characterized.
Researcher notes
The source data identifies the vulnerable method-level access-control pattern and fixed Red Hat cumulative patch levels. It does not provide affected CPEs, broad product inventory data, or detailed exploit telemetry beyond CISA KEV status.
Mitigation direction
- Upgrade JBoss EAP 4.2 to 4.2.0.CP09 or later.
- Upgrade JBoss EAP 4.3 to 4.3.0.CP08 or later.
- Restrict JMX-Console access to trusted administrative networks only.
- Remove or disable JMX-Console where it is not operationally required.
- Review Red Hat advisories for environment-specific update guidance.
Validation and detection
- Inventory systems running Red Hat JBoss EAP 4.2 or 4.3.
- Confirm whether JMX-Console is deployed and reachable.
- Verify installed cumulative patch level against fixed versions.
- Review web logs for unusual HTTP methods targeting JMX-Console.
- Confirm controls block unauthorized methods before console handlers execute.
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-749: 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-2010-0738 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
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- Yes
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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.
CISA KEV status
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2010:0379CVE reference · vendor-advisory, x_refsource_REDHAT
- RHSA-2010:0378CVE reference · vendor-advisory, x_refsource_REDHAT
- https://bugzilla.redhat.com/show_bug.cgi?id=574105CVE reference · x_refsource_CONFIRM
- RHSA-2010:0376CVE reference · vendor-advisory, x_refsource_REDHAT
- RHSA-2010:0377CVE reference · vendor-advisory, x_refsource_REDHAT
- jboss-jmxconsole-security-bypass(58147)CVE reference · vdb-entry, x_refsource_XF
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2010-0738CVE reference · government-resource
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.
Exposed Dangerous Method or Function
Exposed Dangerous Method or Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.