← Back
CVE-2024-45409
Vulnerability in ruby-saml (CVE-2024-45409)
Summary
vulnerability in ruby-saml (CVE-2024-45409). Confidential information can be exposed externally. Mitigation: upgrade to `1.17.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-45409** has been found in ruby-saml.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade ruby-saml to **1.17.0** or later.
If unsure, ask your IT team or search "ruby-saml CVE-2024-45409" on the vendor's site.
CVE-2024-45409 (ruby-saml) — CWE-347 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `1.17.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-347) exists in ruby-saml.
📍 Affected scope
ruby-saml — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.17.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'ruby-saml' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'ruby-saml' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `ruby-saml` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade ruby-saml to 1.17.0ステージング環境で 1.17.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
RubyGems
ruby-saml
[{"type":"ECOSYSTEM","events":[{"introduced":"1.13.0"},{"fixed":"1.17.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-45409
- package https://github.com/SAML-Toolkits/ruby-saml
- web https://github.com/SAML-Toolkits/ruby-saml/security/advisories/GHSA-jw9c-mfg7-9rx2
- web https://github.com/omniauth/omniauth-saml/security/advisories/GHSA-cvp8-5r8g-fhvq
- web https://github.com/SAML-Toolkits/ruby-saml/commit/1ec5392bc506fe43a02dbb66b68741051c5ffeae
- web https://github.com/SAML-Toolkits/ruby-saml/commit/4865d030cae9705ee5cdb12415c654c634093ae7
- web https://github.com/omniauth/omniauth-saml/commit/4274e9d57e65f2dcaae4aa3b2accf831494f2ddd
- web https://github.com/rubysec/ruby-advisory-db/blob/master/gems/omniauth-saml/CVE-2024-45409.yml
- web https://github.com/rubysec/ruby-advisory-db/blob/master/gems/omniauth-saml/GHSA-cvp8-5r8g-fhvq.yml
- web https://github.com/rubysec/ruby-advisory-db/blob/master/gems/ruby-saml/CVE-2024-45409.yml