First published: Tue Sep 10 2024(Updated: )
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 was reported by ahacker1 of SecureSAML (ahacker1@securesaml.com)
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
rubygems/ruby-saml | >=1.13.0<1.17.0 | 1.17.0 |
rubygems/ruby-saml | <1.12.3 | 1.12.3 |
OneLogin Ruby-SAML | <1.12.3 | |
OneLogin Ruby-SAML | >=1.13.0<1.17.0 | |
Omniauth Omniauth Saml Ruby | <=1.10.3 | |
Omniauth Omniauth Saml Ruby | =2.0.0 | |
Omniauth Omniauth Saml Ruby | =2.1.0 | |
GitLab GitLab | <16.11.10 | |
GitLab GitLab | >=17.0.0<17.0.8 | |
GitLab GitLab | >=17.1.0<17.1.8 | |
GitLab GitLab | >=17.2.0<17.2.7 | |
GitLab GitLab | >=17.3.0<17.3.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.