Security readout for executives and security teams
Plain-English summary
This vulnerability affects older Red Hat JBoss products where EJB code may ignore roles declared with the @RunAs annotation. In business terms, an application’s intended internal permission boundary may not behave as designed, creating risk in legacy Java middleware that still supports important workflows.
Executive priority
Prioritize assessment if affected JBoss versions support business-critical or externally reachable applications. The public record lacks severity data, but authorization boundary failures in legacy middleware can carry meaningful operational risk.
Technical view
The CVE states that an EJB method in multiple Red Hat JBoss products ignores roles specified using @RunAs. The record does not provide CVSS, CWE, exploit prerequisites, patch details, or affected configurations beyond listed product families and versions.
Likely exposure
Exposure is most likely in legacy environments still running Red Hat JBoss BRMS 5, EAP 5, JBoss ON 3.1, Portal 4/5, SOA Platform 4.2/4.3/5, or Enterprise Web Server 1.
Exploitation context
The provided sources do not show CISA KEV listing, active exploitation, public exploit evidence, or exploitation mechanics. Treat this as an authorization-behavior issue requiring inventory validation, not as confirmed exploited-in-the-wild activity.
Researcher notes
Evidence is sparse. Official sources identify an EJB @RunAs role-handling issue across several Red Hat JBoss product lines, but do not include CVSS, CWE, patch identifiers, or exploit details in the supplied bundle.
Mitigation direction
- Inventory affected Red Hat JBoss products and versions in production and support environments.
- Check Red Hat CVE guidance and errata for fixes, mitigations, or supported upgrade paths.
- Prioritize replacement or isolation of unsupported legacy JBoss deployments.
- Review applications relying on EJB @RunAs authorization behavior.
Validation and detection
- Confirm deployed JBoss product names and versions against the affected list.
- Identify applications using EJB methods and @RunAs role assumptions.
- Review Red Hat advisories for product-specific remediation status.
- Verify compensating access controls around affected application tiers.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2012-5626 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-5626CVE reference · x_refsource_CONFIRM
- https://access.redhat.com/security/cve/cve-2012-5626CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.