Loading vulnerability…
CVE-2024-45409 is a critical authentication bypass vulnerability in the Ruby-SAML library, affecting versions up to 1.12.2 and 1.13.0 through 1.16.0. The flaw arises from improper verification of SAML Response signatures during SAML assertion validation. Specifically, the library uses an overly permissive XPath selector when extracting digest data, allowing a forged document to supply an attacker-controlled digest value from an unexpected location in the XML document rather than the intended signed reference context. Because the SignedInfo signature can remain valid while digest verification is performed against attacker-controlled data, an attacker can tamper with SAML Response or Assertion contents without invalidating signature checks. In practice, this enables forgery of SAML assertions containing arbitrary identity attributes and impersonation of arbitrary users in applications that rely on the vulnerable library for SAML-based authentication, including deployments using omniauth-saml.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a Python exploit script (CVE-2024-45409.py) and a README.md. The exploit targets CVE-2024-45409, a vulnerability in GitLab's SAML authentication implementation (Ruby-SAML), allowing an attacker with access to any signed SAML document from the IDP to forge a SAML Response and authenticate as any user, including admin, on vulnerable GitLab CE/EE versions. The script takes a captured SAML Response, modifies the XML to move the signature, patch IDs and NameID, update assertion conditions, and inject a malicious reference with a forged DigestValue. The output is a patched SAML Response that can be submitted to the GitLab SAML authentication endpoint (/users/auth/saml/callback). The README provides detailed usage instructions, affected versions, and references. The exploit is a proof-of-concept and requires the attacker to have a valid SAML Response from the IDP. No fake or destructive code is present; the repository is focused on demonstrating the authentication bypass vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Critical improper verification of cryptographic signature vulnerability in Ruby-SAML that can enable SAML authentication bypass via signature wrapping/parser differential issues.
A previously patched SAML-related authentication vulnerability referenced as part of GitLab's security history.
An authentication bypass vulnerability in GitLab with SAML-based authentication, allowing attackers to gain access as any user. Exploit code is publicly available.
Authentication bypass in Ruby-SAML/OmniAuth-SAML due to incorrect XML signature/digest verification logic (XPath selection of DigestValue from anywhere in the document), enabling signature-wrapping style manipulation of SAML responses and unauthorized access (notably impacting GitLab SAML SSO).
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.