Wildfly: wildfly-iiop: wildfly-ejb3: wildfly: authentication bypass on iiop ejb invocations as csiv2 ittprincipalname accepted without transport binding
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
WildFly, including its wildfly-iiop and wildfly-ejb3 components, is affected by this flaw in its IIOP-based EJB invocation handling. A remote, unauthenticated attacker who can reach the IIOP port could impersonate any user and invoke remote EJBs that are exposed over IIOP, bypassing authentication.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A flaw was found in Wildfly. A remote attacker can bypass authentication on IIOP EJB invocations as the CSIv2 security interceptor accepts ITTPrincipalName identity assertions in the service context without verifying transport-level authentication, allowing a pre-auth attacker on the port 3528 to impersonate any principal on every IIOP-exposed @Remote EJB.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- wildfly-iiop-openjdk
Version range not reported
- wildfly-ee-dist
Version range not reported
- wildfly-iiop-openjdk
Version range not reported
- wildfly-iiop-openjdk
Version range not reported
- wildfly-iiop-openjdk
Version range not reported
- wildfly-iiop-openjdk
Version range not reported