SAML AudienceRestriction validation bypass in Apache CXF Fediz plugins
Apache CXF Fediz application plugins (including fediz-spring and fediz-spring2) in versions 1.2.x before 1.2.3 and 1.3.x before 1.3.1 fail to match/validate SAML AudienceRestriction values against the configured audience URIs. As a result, an attacker can present a crafted SAML token that carries a trusted signature but contains AudienceRestriction values that should not be accepted by the relying party, enabling bypass of intended audience-based restrictions.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Remote attackers can bypass intended SAML AudienceRestriction-based access controls/restrictions by supplying a crafted, validly signed SAML token, potentially enabling unauthorized access and other unspecified downstream impacts depending on the protected application’s authorization model.
If you can’t patch tonight, do this now.
No specific workaround is described beyond upgrading. As compensating controls prior to upgrade, restrict SAML token acceptance to trusted identity providers and enforce stricter SAML validation at an upstream gateway/IdP layer where feasible.
Patch, then assume compromise.
Upgrade Apache CXF Fediz to a fixed release: 1.2.3+ for the 1.2.x line, or 1.3.1+ for the 1.3.x line.
No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.