Cyber Resilience

CVE-2024-45409

Gitlab ≤ 16.11.10

Published
10 September 2024
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 10.0
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
EPSS Score 0.11 95th percentile
Risk Priority 91 floored blend · peak EPSS

Summary

CVE-2024-45409 is a critical-severity Improper Verification of Cryptographic Signature (CWE-347) vulnerability in Gitlab Gitlab. Its CVSS base score is 10.0 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Supply Chain Compromise (T1195); ranked in the top 5% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SC-13 (Cryptographic Protection) and SI-7 (Software, Firmware, and Information Integrity) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

The Ruby SAML library, used to implement the client side of SAML authorization in Ruby applications, is affected by CVE-2024-45409. Versions up to 1.12.2 and from 1.13.0 through 1.16.0 fail to properly verify the signature on SAML Responses, as identified under CWE-347. This allows an attacker in possession of any valid signed document from the identity provider to craft a forged Response or Assertion containing arbitrary attributes or subject information.

An unauthenticated remote attacker with access to a legitimately signed SAML document can exploit the flaw to bypass authentication entirely. By submitting the manipulated Response to a vulnerable service provider, the attacker can assume the identity of any user within the application, achieving full account takeover without needing valid credentials or interaction from the target.

The issue is resolved in ruby-saml 1.17.0 and 1.12.3, with patches available via the referenced GitHub commits. Security advisories from the ruby-saml and omniauth-saml projects, along with downstream notifications such as the Debian LTS announcement, recommend immediate upgrade to a fixed release. The EPSS score has remained at its peak of 0.4464 since disclosure with no subsequent increase.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-347

Related Threats

MITRE ATT&CK Enterprise Techniques

T1195 Supply Chain Compromise Initial Access
Adversaries may manipulate products or product delivery mechanisms prior to receipt by a final consumer for the purpose of data or system compromise.
attack.mitre.org →
T1195.002 Compromise Software Supply Chain Initial Access
Adversaries may manipulate application software prior to receipt by a final consumer for the purpose of data or system compromise.
attack.mitre.org →
T1542 Pre-OS Boot Stealth
Adversaries may abuse Pre-OS Boot mechanisms as a way to establish persistence on a system.
attack.mitre.org →
T1553 Subvert Trust Controls Defense Impairment
Adversaries may undermine security controls that will either warn users of untrusted activity or prevent execution of untrusted programs.
attack.mitre.org →
T1553.002 Code Signing Defense Impairment
Adversaries may create, acquire, or steal code signing materials to sign their malware or tools.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-2030Same product: Gitlab Gitlab
CVE-2025-66568Same product: Onelogin Ruby-Saml
CVE-2023-1204Same product: Gitlab Gitlab
CVE-2025-66567Same product: Onelogin Ruby-Saml
CVE-2025-25292Same product: Omniauth Omniauth Saml
CVE-2025-25291Same product: Omniauth Omniauth Saml
CVE-2025-25293Same product: Omniauth Omniauth Saml
CVE-2026-5050Shared CWE-347
CVE-2026-48558Shared CWE-347
CVE-2026-23967Shared CWE-347

Affected Assets

onelogin
ruby-saml
≤ 1.12.3 · 1.13.0 — 1.17.0
omniauth
omniauth saml
2.0.0, 2.1.0 · ≤ 1.10.3
gitlab
gitlab
≤ 16.11.10 · 17.0.0 — 17.0.8 · 17.1.0 — 17.1.8

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 14 hardening rules · 5 OS baselines
Validate
Prove the fix (OWASP ASVS)

—

Mitigating Controls (NIST 800-53 r5) AI

SC-13 Cryptographic Protection good match

Requiring cryptographic protection mechanisms forces correct signature verification to be implemented for data protection.

SI-7 Software, Firmware, and Information Integrity good match

Mandating integrity verification tools directly requires proper cryptographic signature checking to detect unauthorized changes.

SC-23 Session Authenticity partial match

Protecting session authenticity requires correct verification of cryptographic signatures or equivalent mechanisms.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.DS-01 mostly match
prevents

Digital signatures are explicitly cited to protect integrity of data-at-rest, so proper verification directly mitigates the weakness.

PR.DS-02 mostly match
prevents

Digital signatures are explicitly cited to protect integrity of data-in-transit, so proper verification directly mitigates the weakness.

ID.RA-09 partial match
prevents

Requires assessing authenticity and integrity of acquired assets, which commonly relies on signature verification but is limited to pre-acquisition.

PR.PS-06 partial match
prevents

Secure SDLC practices include code signing and signature verification requirements, addressing the weakness during development.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography partial match
prevents

Establishing approved cryptographic solutions and usage practices lowers the probability that signature-verification steps will be omitted or incorrectly implemented.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (2 rules)
  • V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. prevents CWE-347
  • V-248575 OL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-347
Oracle Linux 9 (2 rules)
  • V-271525 OL 9 must have GPG signature verification enabled for all software repositories. prevents CWE-347
  • V-271523 OL 9 must check the GPG signature of locally installed software packages before installation. prevents CWE-347
RHEL 7 (2 rules)
  • V-204447 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-347
  • V-204448 The Red Hat Enterprise Linux operating system must prevent the installation of software, patches, service packs, device drivers, or operating system components of local packages without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-347
RHEL 8 (1 rule)
  • V-230264 RHEL 8 must prevent the installation of software, patches, service packs, device drivers, or operating system components from a repository without verification they have been digitally signed using a certificate that is issued by a Certificate Authority (CA) that is recognized and approved by the organization. prevents CWE-347
RHEL 9 (1 rule)
  • V-257822 RHEL 9 must have GPG signature verification enabled for all software repositories. prevents CWE-347

References