CVE-2011-4085: The servlets invoked by httpha-invoker in JBoss Enterprise Application Platform before 5.1.2, SOA Platform before 5.2.0, BRMS Platform…
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.9% (FIRST EPSS); higher than 87.3% of all records.
- Fixed version: apache-cxf (Red Hat:jboss_enterprise_application_platform:5::el4) 0:2.2.12-4.patch_02.1.1.ep5.el4; cglib (Red Hat:jboss_enterprise_application_platform:5::el4) 0:2.2-5.3.ep5.el4; facelets (Red Hat:jboss_enterprise_application_platform:5::el4) 0:1.1.15-3.B1_patch_01.2.ep5.el4.
Low priority for now. Upgrade to apache-cxf (Red Hat:jboss_enterprise_application_platform:5::el4) 0:2.2.12-4.patch_02.1.1.ep5.el4; cglib (Red Hat:jboss_enterprise_application_platform:5::el4) 0:2.2-5.3.ep5.el4; facelets (Red Hat:jboss_enterprise_application_platform:5::el4) 0:1.1.15-3.B1_patch_01.2.ep5.el4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The servlets invoked by httpha-invoker in JBoss Enterprise Application Platform before 5.1.2, SOA Platform before 5.2.0, BRMS Platform before 5.3.0, and Portal Platform before 4.3 CP07 perform access control only for the GET and POST methods, which allow remote attackers to bypass authentication by sending a request with a different method. NOTE: this vulnerability exists because of a CVE-2010-0738 regression.
- Published
- Nov 23, 2012
- Updated
- Jun 16, 2026
- EPSS
- 2.9% · 87th percentile
- CWE
- CWE-287
Report tools
Action score
28
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| redhat | jboss enterprise application platform | cpe:2.3:a:redhat:jboss_enterprise_application_platform |
| redhat | jboss enterprise soa platform | cpe:2.3:a:redhat:jboss_enterprise_soa_platform |
| redhat | jboss enterprise brms platform | cpe:2.3:a:redhat:jboss_enterprise_brms_platform |
| redhat | jboss enterprise portal platform | cpe:2.3:a:redhat:jboss_enterprise_portal_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 platformup to 5.1.1 inclusive
- redhat jboss enterprise application platform4.2.0
- redhat jboss enterprise application platform4.3.0
- redhat jboss enterprise application platform5.0.0
- redhat jboss enterprise application platform5.0.1
- redhat jboss enterprise application platform5.1.0
- redhat jboss enterprise brms platformup to 5.2.0 inclusive
- redhat jboss enterprise portal platformup to 4.3.0 inclusive
+7 more rows
- redhat jboss enterprise soa platformup to 5.1.1 inclusive
- redhat jboss enterprise soa platform4.2.0
- redhat jboss enterprise soa platform4.3.0
- redhat jboss enterprise soa platform5.0.0
- redhat jboss enterprise soa platform5.0.1
- redhat jboss enterprise soa platform5.0.2
- redhat jboss enterprise soa platform5.1.0
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:5::el4 | apache-cxf | before 0:2.2.12-4.patch_02.1.1.ep5.el4 | 0:2.2.12-4.patch_02.1.1.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | cglib | before 0:2.2-5.3.ep5.el4 | 0:2.2-5.3.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | facelets | before 0:1.1.15-3.B1_patch_01.2.ep5.el4 | 0:1.1.15-3.B1_patch_01.2.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | glassfish-jaxb | before 0:2.1.12-10_patch_02.ep5.el4 | 0:2.1.12-10_patch_02.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | glassfish-jsf | before 0:1.2_13-5_patch_01.3.ep5.el4 | 0:1.2_13-5_patch_01.3.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jacorb-jboss | before 0:2.3.1-10.patch_03.4.ep5.el4 | 0:2.3.1-10.patch_03.4.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jakarta-commons-logging-jboss | before 0:1.1-10.3_patch_02.1.ep5.el4 | 0:1.1-10.3_patch_02.1.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-aop2 | before 0:2.1.6-2.CP03.1.1.ep5.el4 | 0:2.1.6-2.CP03.1.1.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-cache-core | before 0:3.2.8-1.ep5.el4 | 0:3.2.8-1.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-cl | before 0:2.0.10-1.2.ep5.el4 | 0:2.0.10-1.2.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-cluster-ha-client | before 0:1.1.4-1.1.ep5.el4 | 0:1.1.4-1.1.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-common-core | before 0:2.2.18-1.1.ep5.el4 | 0:2.2.18-1.1.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-eap5-native | before 0:5.1.2-1.4.ep5.el4 | 0:5.1.2-1.4.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-ejb3-core | before 0:1.3.8-0.1.ep5.el4 | 0:1.3.8-0.1.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-ejb3-proxy-clustered | before 0:1.0.3-2.SP1.1.ep5.el4 | 0:1.0.3-2.SP1.1.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-ejb3-proxy-impl | before 0:1.0.6-2.SP2.1.ep5.el4 | 0:1.0.6-2.SP2.1.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-el | before 0:1.0_02-0.CR6.2.ep5.el4 | 0:1.0_02-0.CR6.2.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-messaging | before 0:1.4.8-9.SP5.1.ep5.el4 | 0:1.4.8-9.SP5.1.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-naming | before 0:5.0.3-3.CP01.3.1.ep5.el4 | 0:5.0.3-3.CP01.3.1.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-remoting | before 0:2.5.4-9.SP3.1.ep5.el4 | 0:2.5.4-9.SP3.1.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-seam2 | before 0:2.2.5.EAP5-6.ep5.el4 | 0:2.2.5.EAP5-6.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-seam2-docs | before 0:2.2.5.EAP5-6.ep5.el4 | 0:2.2.5.EAP5-6.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-seam2-examples | before 0:2.2.5.EAP5-6.ep5.el4 | 0:2.2.5.EAP5-6.ep5.el4 |
| Red Hat:jboss_enterprise_application_platform:5::el4 | jboss-seam2-runtime | before 0:2.2.5.EAP5-6.ep5.el4 | 0:2.2.5.EAP5-6.ep5.el4 |
+96
Same product
redhat: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-12149In Jboss Application Server as shipped with Red Hat Enterprise Application Platform 5.2, it was found that the doFilter method in the…KEV96Now
- CVE-2010-1871JBoss Seam 2 (jboss-seam2), as used in JBoss Enterprise Application Platform 4.3.0 for Red Hat Linux, does not properly sanitize inputs for…KEV90Now
- CVE-2010-1428The Web Console (aka web-console) in JBossAs in Red Hat JBoss Enterprise Application Platform (aka JBoss EAP or JBEAP) 4.2 before…KEV76This week
Published before and after this one in the same product
- ← EarlierCVE-2011-4608Jan 27, 2012 · mod_cluster in JBoss Enterprise Application Platform 5.1.2 for Red Hat Linux allows worker nodes to register with arbitrary virtual hosts…31Monitor
- ← EarlierCVE-2012-1154Oct 22, 2012 · mod_cluster 1.0.10 before 1.0.10 CP03 and 1.1.x before 1.1.4, as used in JBoss Enterprise Application Platform 5.1.2, when "ROOT" is set to…18Monitor
- Later →CVE-2011-4605Nov 23, 2012 · The (1) JNDI service, (2) HA-JNDI service, and (3) HAJNDIFactory invoker servlet in JBoss Enterprise Application Platform 4.3.0 CP10 and…31Monitor
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:apache-cxf | 0:2.2.12-4.patch_02.1.ep5.el6 · Red Hat:jboss_enterprise_application_platform:5::el6 | Package registry (OSV) |
| red hat:cglib | 0:2.2-5.5.ep5.el6 · Red Hat:jboss_enterprise_application_platform:5::el6 | Package registry (OSV) |
| red hat:facelets | 0:1.1.15-3.B1_patch_01.2.ep5.el6 · Red Hat:jboss_enterprise_application_platform:5::el6 | Package registry (OSV) |
| red hat:glassfish-jaxb | 0:2.1.12-10_patch_02.ep5.el6 · Red Hat:jboss_enterprise_application_platform:5::el6 | Package registry (OSV) |
| red hat:glassfish-jsf | 0:1.2_13-5_patch_01.3.ep5.el6 · Red Hat:jboss_enterprise_application_platform:5::el6 | Package registry (OSV) |
| red hat:jacorb-jboss | 0:2.3.1-10.patch_03.4.ep5.el6 · Red Hat:jboss_enterprise_application_platform:5::el6 | Package registry (OSV) |
| red hat:jakarta-commons-logging-jboss | 0:1.1-10.3_patch_02.1.ep5.el6 · Red Hat:jboss_enterprise_application_platform:5::el6 | Package registry (OSV) |
| red hat:jboss-aop2 | 0:2.1.6-2.CP03.1.1.ep5.el6 · Red Hat:jboss_enterprise_application_platform:5::el6 | Package registry (OSV) |
| red hat:jboss-cache-core | 0:3.2.8-1.ep5.el6 · Red Hat:jboss_enterprise_application_platform:5::el6 | Package registry (OSV) |
| red hat:jboss-cl | 0:2.0.10-1.2.ep5.el6 · Red Hat:jboss_enterprise_application_platform:5::el6 | Package registry (OSV) |
| red hat:jboss-cluster-ha-client | 0:1.1.4-1.1.ep5.el6 · Red Hat:jboss_enterprise_application_platform:5::el6 | Package registry (OSV) |
| red hat:jboss-common-core | 0:2.2.18-1.1.ep5.el6 · Red Hat:jboss_enterprise_application_platform:5::el6 | 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.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);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)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- rhn.redhat.com/errata/RHSA-2011-1798.html
- rhn.redhat.com/errata/RHSA-2011-1799.html
- rhn.redhat.com/errata/RHSA-2011-1800.html
- rhn.redhat.com/errata/RHSA-2011-1805.html
- rhn.redhat.com/errata/RHSA-2011-1822.html
- rhn.redhat.com/errata/RHSA-2012-0091.html
- rhn.redhat.com/errata/RHSA-2012-1028.html
- secunia.com/advisories/47169
- secunia.com/advisories/47866
- bugzilla.redhat.com/show_bug.cgi?id=750422
Vendor advisories and official records. Exploit/PoC links are deliberately left out.