# CVE-2012-5626: Missing authorization in JBoss BRMS

> Attackers can bypass role restrictions on EJB methods in Red Hat JBoss products, potentially gaining unauthorized access or privileges.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jan 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jmm8-g2w4-4fc4

## What is CVE-2012-5626?

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

### Official description

EJB method in Red Hat JBoss BRMS 5; Red Hat JBoss Enterprise Application Platform 5; Red Hat JBoss Operations Network 3.1; Red Hat JBoss Portal 4 and 5; Red Hat JBoss SOA Platform 4.2, 4.3, and 5; in Red Hat JBoss Enterprise Web Server 1 ignores roles specified using the @RunAs annotation.

## Which versions are affected by CVE-2012-5626?

It affects 6 products.


Products: Redhat Jboss Brms, Redhat Jboss Enterprise Application Platform, Redhat Jboss Enterprise Web Server, Redhat Jboss Operations Network, Redhat Jboss Portal, Redhat Jboss Soa Platform.

## How do I fix CVE-2012-5626?

No fix has been published for CVE-2012-5626 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-5626 being exploited?

There is no known exploitation of CVE-2012-5626 in the wild and no public exploit code.

## Other vulnerabilities in Redhat Jboss Enterprise Application Platform

- [CVE-2016-7041](https://insights.sbomify.com/CVE-2016-7041/): Path traversal in Drools Workbench (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-5626 and fix it if it is affected.

What it is: CVE-2012-5626 is a high-severity missing authorization vulnerability in Redhat Jboss Enterprise Application Platform, published on 23 Jan 2020. 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-5626 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-2012-5626/ (Markdown: https://insights.sbomify.com/CVE-2012-5626/index.md)
```

## Sources

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

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