The Ruby SAML library vulnerable to a SAML authentication bypass via Incorrect XPath selector
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 12%. Fixed in GitLab 16.11.10, GitLab 17.0.8, GitLab 17.1.8 and 4 more.
The Ruby SAML library is for implementing the client side of a SAML authorization. Ruby-SAML in <= 12.2 and 1.13.0 <= 1.16.0 does not properly verify the signature of the SAML Response. An unauthenticated attacker with access to any signed saml document (by the IdP) can thus forge a SAML Response/Assertion with arbitrary contents. This would allow the attacker to log in as arbitrary user within the vulnerable system. This vulnerability is fixed in 1.17.0 and 1.12.3.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| GitLab | GitLab | <16.11.10, >=17.0.0 <17.0.8, >=17.1.0 <17.1.8, >=17.2.0 <17.2.7, >=17.3.0 <17.3.3 | 16.11.10, 17.0.8, 17.1.8, 17.2.7, 17.3.3 |
| SAML-Toolkits | >=1.13.0 <1.17.0, <1.12.3 | ||
| omniauth | omniauth_saml | =2.1.0, <=1.10.3, =2.0.0 | |
| onelogin | ruby-saml | <1.12.3, >=1.13.0 <1.17.0 | 1.12.3, 1.17.0 |
Exploit evidence
2 public sources
Vendor advisories
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in GitLab, strongest first
Embed
A live severity badge for an advisory, README or ticket