CVE-2024-45409 in the critical feed json
The Ruby SAML library vulnerable to a SAML authentication bypass via Incorrect XPath selector
published 2024-09-10 2 y ago modified 2026-11-04 5 d ago also BIT-gitlab-2024-45409 , EUVD-2024-2828 , GHSA-jw9c-mfg7-9rx2
- cvss
- 10.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 10.7%
- EPSS 10.7% chance of exploitation in 30 days, percentile 95%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- rubygems ruby-saml 1.12.3, 1.17.0
- bitnami gitlab 16.11.10, 17.0.8, 17.1.8, 17.2.7, 17.3.3
- onelogin ruby-saml 1.12.3, 1.17.0
- ruby-saml Debian 12 1.13.0-1+deb12u1
debian advisories DEBIAN-CVE-2024-45409
- ruby-saml Ubuntu 20.04 LTS 1.11.0-1ubuntu0.1
- ruby-saml Ubuntu 22.04 LTS 1.13.0-1ubuntu0.1
- ruby-saml Ubuntu 24.04 LTS 1.15.0-1ubuntu0.24.04.1
- ruby-saml Ubuntu Pro 16.04 LTS 1.1.2-1ubuntu1+esm1
- ruby-saml Ubuntu Pro 18.04 LTS 1.7.2-1ubuntu0.1~esm1
ubuntu advisories UBUNTU-CVE-2024-45409
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
10.68% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N |
| GitHub | 3.1 | 10.0 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| rubygems | ruby-saml | <1.12.3 >=1.13.0, <1.17.0 |
1.12.3 1.17.0 |
| bitnami | 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 |
Affected products
- SAML-Toolkits ruby-saml
- onelogin ruby-saml
- omniauth omniauth-saml
Classification
- Weakness
-
- CWE-347 Improper Verification of Cryptographic Signature
- Technology feeds
References
-
github.com
/SAML-Toolkits/ruby-saml/commit/1ec5392bc506fe43a02dbb66b68741051c5ffeae
web, patch
-
github.com
/SAML-Toolkits/ruby-saml/commit/4865d030cae9705ee5cdb12415c654c634093ae7
web, patch
-
github.com
/omniauth/omniauth-saml/commit/4274e9d57e65f2dcaae4aa3b2accf831494f2ddd
web
-
github.com
/SAML-Toolkits/ruby-saml/security/advisories/GHSA-jw9c-mfg7-9rx2
web, vendor-advisory, advisory
-
github.com
/omniauth/omniauth-saml/security/advisories/GHSA-cvp8-5r8g-fhvq
web, vendor-advisory, advisory
-
ssoready.com
/blog/engineering/ruby-saml-pwned-by-xml-signature-wrapping-attacks/
web
-
news.ycombinator.com
/item?id=41586031
web
-
security.netapp.com
/advisory/ntap-20240926-0008/
web
-
lists.debian.org
/debian-lts-announce/2024/11/msg00006.html
web
-
nvd.nist.gov
/vuln/detail/CVE-2024-45409
advisory, web
-
github.com
/SAML-Toolkits/ruby-saml
package
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/omniauth-saml/CVE-2024-45409.yml
web
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/omniauth-saml/GHSA-cvp8-5r8g-fhvq.yml
web
-
github.com
/rubysec/ruby-advisory-db/blob/master/gems/ruby-saml/CVE-2024-45409.yml
web
Sources
- CVE List CVE-2024-45409
- GitHub Advisory GHSA-jw9c-mfg7-9rx2
- NVD CVE-2024-45409
- OSV BIT-gitlab-2024-45409
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.