CVE-2024-45409: 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 ...

Description

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.

Metrics

CVSS 3.1

9.8/10

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS Probability

10.68%

95.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-347

Affected Software

Vendor	Product	Versions
Onelogin	Ruby-Saml	< 1.12.3
Onelogin	Ruby-Saml	>= 1.13.0, < 1.17.0
Omniauth	Omniauth Saml	<= 1.10.3
Omniauth	Omniauth Saml	2.0.0
Omniauth	Omniauth Saml	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

References

Timeline

Published: Sep 10, 2024
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2024-45409?

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.

How severe is CVE-2024-45409?

CVE-2024-45409 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 10.68% probability of exploitation in the next 30 days.

How do I fix CVE-2024-45409?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.