First published: Tue Sep 10 2024(Updated: )
Last updated 23 September 2024
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 | <1.12.3 | |
OneLogin | >=1.13.0<1.17.0 | |
Omniauth SAML Ruby | <=1.10.3 | |
Omniauth SAML Ruby | =2.0.0 | |
Omniauth SAML Ruby | =2.1.0 | |
GitLab | <16.11.10 | |
GitLab | >=17.0.0<17.0.8 | |
GitLab | >=17.1.0<17.1.8 | |
GitLab | >=17.2.0<17.2.7 | |
GitLab | >=17.3.0<17.3.3 | |
debian/ruby-saml | <=1.11.0-1 | 1.11.0-1+deb11u1 1.13.0-1+deb12u1 1.17.0-1 |
IBM Aspera Shares | <=1.9.9 - 1.10.0 PL7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-45409 has been assigned a high severity rating due to its potential for allowing unauthenticated attackers to forge SAML Responses.
To fix CVE-2024-45409, upgrade ruby-saml to version 1.17.0 or 1.12.3 or higher.
Versions of Ruby-SAML from 1.0.0 to 1.16.0 are affected by CVE-2024-45409.
Yes, CVE-2024-45409 can be exploited remotely by attackers who have access to any signed SAML document.
No, CVE-2024-45409 can be exploited by unauthenticated attackers.