# CVE-2012-1154: Improper Access Control in JBoss mod_cluster > Remote attackers can bypass access restrictions and access root context applications when excludedContexts is configured, affecting JBoss Enterprise Application Platform. - **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 22 Oct 2012 - **Updated:** 6 Aug 2024 - **Also known as:** GHSA-v2fp-h4qx-x3r6, RHSA-2012:1052, RHSA-2012:1053, RHSA-2012:1166 ## What is CVE-2012-1154? CVE-2012-1154 is a medium-severity authentication bypass vulnerability in Redhat Jboss Enterprise Application Platform, published on 22 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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 excludedContexts, exposes the root context of the server, which allows remote attackers to bypass access restrictions and gain access to applications deployed on the root context via unspecified vectors. Weakness: CWE-264 ## Which versions are affected by CVE-2012-1154? 2 open source packages ship an affected version, including org.jboss.mod_cluster:mod_cluster. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.jboss.mod_cluster:mod_cluster` | Maven | From 1.1.0 | 1.1.4 | | `org.jboss.mod_cluster:mod_cluster` | Maven | From 1.1.0 | 1.1.4 | | `mod_cluster` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:1.0.10-4.GA_CP02_patch01.ep5.el4 | | `mod_cluster-demo` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:1.0.10-4.GA_CP02_patch01.ep5.el4 | | `mod_cluster-jbossas` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:1.0.10-4.GA_CP02_patch01.ep5.el4 | | `mod_cluster-jbossweb2` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:1.0.10-4.GA_CP02_patch01.ep5.el4 | | `mod_cluster-tomcat6` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:1.0.10-4.GA_CP02_patch01.ep5.el4 | | `mod_cluster` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster-demo` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster-jbossas` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster-jbossweb2` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster-tomcat6` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster-demo` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster-jbossas` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster-jbossweb2` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster-tomcat6` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster` | Red Hat:jboss_enterprise_web_platform:5::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster-demo` | Red Hat:jboss_enterprise_web_platform:5::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster-jbossas` | Red Hat:jboss_enterprise_web_platform:5::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster-jbossweb2` | Red Hat:jboss_enterprise_web_platform:5::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster-tomcat6` | Red Hat:jboss_enterprise_web_platform:5::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster` | Red Hat:jboss_enterprise_web_platform:5::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster-demo` | Red Hat:jboss_enterprise_web_platform:5::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster-jbossas` | Red Hat:jboss_enterprise_web_platform:5::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster-jbossweb2` | Red Hat:jboss_enterprise_web_platform:5::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster-tomcat6` | Red Hat:jboss_enterprise_web_platform:5::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster` | Red Hat:jboss_enterprise_web_server:1::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster-demo` | Red Hat:jboss_enterprise_web_server:1::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster-jbossas` | Red Hat:jboss_enterprise_web_server:1::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster-jbossweb2` | Red Hat:jboss_enterprise_web_server:1::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster-tomcat6` | Red Hat:jboss_enterprise_web_server:1::el5 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el5 | | `mod_cluster` | Red Hat:jboss_enterprise_web_server:1::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster-demo` | Red Hat:jboss_enterprise_web_server:1::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster-jbossas` | Red Hat:jboss_enterprise_web_server:1::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster-jbossweb2` | Red Hat:jboss_enterprise_web_server:1::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | | `mod_cluster-tomcat6` | Red Hat:jboss_enterprise_web_server:1::el6 | All versions | 0:1.0.10-4.1.GA_CP02_patch01.ep5.el6 | Products: Redhat Jboss Enterprise Application Platform, Redhat Mod Cluster. ## How do I fix CVE-2012-1154? Upgrade org.jboss.mod_cluster:mod_cluster to 1.1.4 or later. ## Is CVE-2012-1154 being exploited? There is no known exploitation of CVE-2012-1154 in the wild and no public exploit code. ## Other vulnerabilities in Redhat Jboss Enterprise Application Platform - [CVE-2017-12149](https://insights.sbomify.com/CVE-2017-12149/): Red Hat JBoss Application Server Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2010-1428](https://insights.sbomify.com/CVE-2010-1428/): Red Hat JBoss Information Disclosure (medium 5.9, exploited in the wild) - [CVE-2010-0738](https://insights.sbomify.com/CVE-2010-0738/): Red Hat JBoss Authentication Bypass (low 3.7, exploited in the wild) - [CVE-2016-3690](https://insights.sbomify.com/CVE-2016-3690/): Deserialization in n/a (critical 9.8) - [CVE-2017-7504](https://insights.sbomify.com/CVE-2017-7504/): Deserialization in JBoss (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2012-1154 and fix it if it is affected. What it is: CVE-2012-1154 is a medium-severity authentication bypass vulnerability in Redhat Jboss Enterprise Application Platform, published on 22 Oct 2012. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2012-1154 in the wild and no public exploit code. Affected packages and fixed versions: - org.jboss.mod_cluster:mod_cluster (Maven): affected from 1.1.0; fixed in 1.1.4 - org.jboss.mod_cluster:mod_cluster (Maven): affected from 1.1.0; fixed in 1.1.4 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2012-1154/ (Markdown: https://insights.sbomify.com/CVE-2012-1154/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2012-1154 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-1154 - OSV: https://osv.dev/vulnerability/CVE-2012-1154 --- From sbomify Insights: https://insights.sbomify.com/CVE-2012-1154/ Summaries are generated and may contain mistakes; the official description above is the record.