# CVE-2012-3428: User confusion in IronJacamar

> Remote attackers can bypass authentication to access arbitrary datasource connections in JBoss IronJacamar when specific security configurations are enabled.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Dec 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ppg2-ww3w-hq84

## What is CVE-2012-3428?

CVE-2012-3428 is a medium-severity authentication bypass vulnerability in n/a, published on 20 Dec 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The IronJacamar container before 1.0.12.Final for JBoss Application Server, when allow-multiple-users is enabled in conjunction with a security domain, does not use the credentials supplied in a getConnection function call, which allows remote attackers to obtain access to an arbitrary datasource connection in opportunistic circumstances via an invalid connection attempt.

Weakness: CWE-255

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

2 open source packages ship an affected version, including org.jboss.ironjacamar:ironjacamar-jdbc. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jboss.ironjacamar:ironjacamar-jdbc` | Maven | All versions | 1.0.12.Final |
| `org.jboss.ironjacamar:ironjacamar-jdbc` | Maven | All versions | 1.0.12.Final |

Products: Jboss Ironjacamar.

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

Upgrade org.jboss.ironjacamar:ironjacamar-jdbc to 1.0.12.Final or later.

## Is CVE-2012-3428 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-3428 is a medium-severity authentication bypass vulnerability in n/a, published on 20 Dec 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-3428 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jboss.ironjacamar:ironjacamar-jdbc (Maven): affected all versions; fixed in 1.0.12.Final
- org.jboss.ironjacamar:ironjacamar-jdbc (Maven): affected all versions; fixed in 1.0.12.Final

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

## Sources

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

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