How severe is CVE-2012-3428?

No CVSS score has been assigned to CVE-2012-3428 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2012-3428?

CVE-2012-3428 affects the following packages: org.jboss.ironjacamar:ironjacamar-jdbc (Maven). Ecosystems affected: Maven.

How do I fix CVE-2012-3428?

Update org.jboss.ironjacamar:ironjacamar-jdbc to 1.0.12.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-3428 is resolved across your whole dependency graph.

How do I detect CVE-2012-3428 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jboss.ironjacamar:ironjacamar-jdbc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2012-3428 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2012-3428 actively exploited in the wild?

No public exploit code has been indexed for CVE-2012-3428 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2012-3428?

CVE-2012-3428 has an EPSS (Exploit Prediction Scoring System) score of 1.4%, placing it in the 72th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2012-3428?

CVE-2012-3428 is classified as CWE-255 (CWE-255). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2012-3428 published, and has it been updated?

CVE-2012-3428 was published on May 17, 2022 and was last updated on December 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2012-3428: ironjacamar-jdbc — Fixed in 1.0.12.Final

EPSS Exploitation Probability

via FIRST.org ↗

1.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs72th percentile — riskier than 72% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.jboss.ironjacamar:ironjacamar-jdbc

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jboss.ironjacamar:ironjacamar-jdbc`	all versions	1.0.12.Final`org.jboss.ironjacamar:ironjacamar-jdbc:1.0.12.Final`

Affected Products

1 product · 1 configurations

Application

ironjacamarjboss

≤ 1.0.11

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jboss.ironjacamar:ironjacamar-jdbc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jboss.ironjacamar:ironjacamar-jdbc to 1.0.12.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2012-3428 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat JBoss Enterprise Application Platform 6.0	see advisory	RHSA-2012:1594
Red Hat JBoss Enterprise Application Platform 6 for RHEL 5	`antlr-eap6-0:2.7.7-15_redhat_2.ep6.el5`	RHSA-2012:1591
Red Hat JBoss Enterprise Application Platform 6 for RHEL 6	`antlr-eap6-0:2.7.7-15_redhat_2.ep6.el6`	RHSA-2012:1592

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2012-3428 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2012-3428 — ironjacamar-jdbc