LiveActive security incident?Get immediate response
CVE Record

CVE-2012-3428: The IronJacamar container before 1.0.12.Final for JBoss Application Server, when allow-multiple-users is en...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This flaw could let an attacker get a database connection they should not have when a vulnerable JBoss Application Server setup uses IronJacamar with a specific multi-user and security-domain configuration. The source bundle does not provide CVSS, confirmed exploitation, or complete product/version mapping, so urgency depends on whether that configuration exists. Exposure is most likely in legacy JBoss Application Server deployments using IronJacamar before 1.0.12.Final, with allow-multiple-users enabled together with a security domain. Systems without that configuration are less likely to be affected based on the provided description. Treat this as a targeted legacy-platform risk. Prioritize asset discovery and patch confirmation for JBoss systems handling sensitive data, especially where database access crosses user or tenant boundaries. Mitigation focus: Identify JBoss deployments using IronJacamar versions before 1.0.12.Final.; Apply relevant Red Hat or vendor updates for affected JBoss/IronJacamar packages.; Review allow-multiple-users plus security-domain usage against vendor guidance..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2012-3428 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.