Sign inStart freeBook a demo

What is CVE-2024-45409?A critical-severity flaw in Ruby-SAML, explained.

Critical severity3 affected products
The short answer

CVE-2024-45409 is a critical-severity flaw (CVSS 9.8) in Ruby-SAML from Onelogin, published on 10 September 2024. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 11%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 10 September 2024. Record last updated 17 June 2026. We keep this page's data up to date.

What it does

What is CVE-2024-45409? In plain terms.

It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

The official 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.

What kind of flaw is it?

  • CWE-347Improper Verification of Cryptographic Signature
CVSS 3.1 scoreCritical · 9.8

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAnywhere on the internet
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstNo login needed
  • Does someone have to clickNo, nobody has to do anything
  • What an attacker getsCan read data, change data and take it offline

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

Exploitation

Is CVE-2024-45409 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 11%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days11%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Exploit likelihood fell
  3. Exploit likelihood jumped
  4. Record last updated
How Precursor Intelligence ranks it
56out of 100Medium

CVE-2024-45409 scores 56. Action: Plan remediation.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2024-45409 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2024-45409? 3 products.

The published record lists 3 products from 3 vendors. Versions are shown as published: "before 1.12.3" means every version up to, but not including, 1.12.3. If you run one of these, check your version, then go to the fix below.

  • Application

    Ruby-SAML

    by Onelogin

    Affected versions
    before 1.12.31.13.0 to before 1.17.0
  • Application

    GitLab

    by GitLab

    Affected versions
    before 16.11.1017.0.0 to before 17.0.817.1.0 to before 17.1.817.2.0 to before 17.2.717.3.0 to before 17.3.3
  • Application

    Omniauth SAML

    by Omniauth

    Affected versions
    up to 1.10.32.0.02.1.0
Remediation

How do I fix CVE-2024-45409? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

8 links
Precursor Intelligence

Does CVE-2024-45409 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2024-45409 is a critical-severity flaw in Ruby-SAML from Onelogin, published on 10 September 2024. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can read data, change data and take it offline.

It scores 9.8 out of 10 on the CVSS severity scale, which is critical. Our risk score for CVE-2024-45409 is 56 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 11%. That can change at any time, which is why we keep watching.

For Ruby-SAML from Onelogin: before 1.12.3, 1.13.0 to before 1.17.0. The record lists 3 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring