# CVE-2011-4608: Missing authorization in n/a

> Remote attackers can bypass access restrictions in JBoss mod_cluster to register malicious nodes, enabling session hijacking and credential theft.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jan 2012
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3vmm-p7jr-jw44, RHSA-2012:0035, RHSA-2012:0037, RHSA-2012:0039

## What is CVE-2011-4608?

CVE-2011-4608 is a high-severity missing authorization vulnerability in Redhat Jboss Enterprise Application Platform, published on 27 Jan 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mod_cluster in JBoss Enterprise Application Platform 5.1.2 for Red Hat Linux allows worker nodes to register with arbitrary virtual hosts, which allows remote attackers to bypass intended access restrictions and provide malicious content, hijack sessions, and steal credentials by registering from an external vhost that does not enforce security constraints.

Weakness: CWE-264

## Which versions are affected by CVE-2011-4608?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mod_cluster-native` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:1.0.10-4.GA_CP02.ep5.el4 |
| `mod_cluster-native-debuginfo` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:1.0.10-4.GA_CP02.ep5.el4 |
| `mod_cluster-native` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 0:1.0.10-4.1.GA_CP02.ep5.el5 |
| `mod_cluster-native` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 0:1.0.10-4.1.1.GA_CP02.ep5.el6 |
| `mod_cluster-native` | Red Hat:jboss_enterprise_web_platform:5::el5 | All versions | 0:1.0.10-4.1.GA_CP02.ep5.el5 |
| `mod_cluster-native` | Red Hat:jboss_enterprise_web_platform:5::el6 | All versions | 0:1.0.10-4.1.1.GA_CP02.ep5.el6 |
| `mod_cluster` | Red Hat:jboss_enterprise_web_server:1::el4 | All versions | 0:1.0.10-3.GA_CP02.ep5.el4 |
| `mod_cluster-demo` | Red Hat:jboss_enterprise_web_server:1::el4 | All versions | 0:1.0.10-3.GA_CP02.ep5.el4 |
| `mod_cluster-jbossas` | Red Hat:jboss_enterprise_web_server:1::el4 | All versions | 0:1.0.10-3.GA_CP02.ep5.el4 |
| `mod_cluster-jbossweb2` | Red Hat:jboss_enterprise_web_server:1::el4 | All versions | 0:1.0.10-3.GA_CP02.ep5.el4 |
| `mod_cluster-native` | Red Hat:jboss_enterprise_web_server:1::el4 | All versions | 0:1.0.10-4.GA_CP02.ep5.el4 |
| `mod_cluster-native-debuginfo` | Red Hat:jboss_enterprise_web_server:1::el4 | All versions | 0:1.0.10-4.GA_CP02.ep5.el4 |
| `mod_cluster-tomcat6` | Red Hat:jboss_enterprise_web_server:1::el4 | All versions | 0:1.0.10-3.GA_CP02.ep5.el4 |
| `mod_cluster` | Red Hat:jboss_enterprise_web_server:1::el5 | All versions | 0:1.0.10-3.1.GA_CP02.ep5.el5 |
| `mod_cluster-demo` | Red Hat:jboss_enterprise_web_server:1::el5 | All versions | 0:1.0.10-3.1.GA_CP02.ep5.el5 |
| `mod_cluster-jbossas` | Red Hat:jboss_enterprise_web_server:1::el5 | All versions | 0:1.0.10-3.1.GA_CP02.ep5.el5 |
| `mod_cluster-jbossweb2` | Red Hat:jboss_enterprise_web_server:1::el5 | All versions | 0:1.0.10-3.1.GA_CP02.ep5.el5 |
| `mod_cluster-native` | Red Hat:jboss_enterprise_web_server:1::el5 | All versions | 0:1.0.10-4.1.GA_CP02.ep5.el5 |
| `mod_cluster-tomcat6` | Red Hat:jboss_enterprise_web_server:1::el5 | All versions | 0:1.0.10-3.1.GA_CP02.ep5.el5 |
| `mod_cluster` | Red Hat:jboss_enterprise_web_server:1::el6 | All versions | 0:1.0.10-3.2.GA_CP02.ep5.el6 |
| `mod_cluster-demo` | Red Hat:jboss_enterprise_web_server:1::el6 | All versions | 0:1.0.10-3.2.GA_CP02.ep5.el6 |
| `mod_cluster-jbossas` | Red Hat:jboss_enterprise_web_server:1::el6 | All versions | 0:1.0.10-3.2.GA_CP02.ep5.el6 |
| `mod_cluster-jbossweb2` | Red Hat:jboss_enterprise_web_server:1::el6 | All versions | 0:1.0.10-3.2.GA_CP02.ep5.el6 |
| `mod_cluster-native` | Red Hat:jboss_enterprise_web_server:1::el6 | All versions | 0:1.0.10-4.1.1.GA_CP02.ep5.el6 |
| `mod_cluster-tomcat6` | Red Hat:jboss_enterprise_web_server:1::el6 | All versions | 0:1.0.10-3.2.GA_CP02.ep5.el6 |

Products: Redhat Jboss Enterprise Application Platform.

## How do I fix CVE-2011-4608?

Apply the vendor's patch.

## Is CVE-2011-4608 being exploited?

There is no known exploitation of CVE-2011-4608 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-2011-4608 and fix it if it is affected.

What it is: CVE-2011-4608 is a high-severity missing authorization vulnerability in Redhat Jboss Enterprise Application Platform, published on 27 Jan 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-2011-4608 in the wild and no public exploit code.

Affected product: Redhat Jboss Enterprise Application Platform. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-2011-4608/ (Markdown: https://insights.sbomify.com/CVE-2011-4608/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-4608
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-4608
- OSV: https://osv.dev/vulnerability/CVE-2011-4608

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-4608/
Summaries are generated and may contain mistakes; the official description above is the record.
