SAML-Toolkits ruby-saml up to 1.12.2/1.16.x SAML Response signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in SAML-Toolkits ruby-saml up to 1.12.2/1.16.x. It has been classified as critical. The affected element is an unknown function of the component SAML Response Handler. Performing a manipulation results in signature verification. This vulnerability is reported as CVE-2024-45409. The attack is possible to be carried out remotely. Moreover, an exploit is present. Upgrading the affected component is recommended.
Details
A vulnerability was found in SAML-Toolkits ruby-saml up to 1.12.2/1.16.x. It has been classified as critical. This affects an unknown code block of the component SAML Response Handler. The manipulation with an unknown input leads to a signature verification vulnerability. CWE is classifying the issue as CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2024-45409 since 08/28/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are unknown but a public exploit is available.
The exploit is shared for download at packetstormsecurity.com. It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 210743 (Debian dla-3949 : ruby-saml - security update), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 1.12.3 or 1.17.0 eliminates this vulnerability. Applying the patch 1ec5392bc506fe43a02dbb66b68741051c5ffeae is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the vulnerability database at Tenable (210743). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.0VulDB Meta Temp Score: 8.8
VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CNA Base Score: 10.0
CNA Vector (GitHub_M): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Signature verificationCWE: CWE-347 / CWE-345
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 210743
Nessus Name: Debian dla-3949 : ruby-saml - security update
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: ruby-saml 1.12.3/1.17.0
Patch: 1ec5392bc506fe43a02dbb66b68741051c5ffeae
Timeline
08/28/2024 🔍09/11/2024 🔍
09/11/2024 🔍
11/12/2024 🔍
Sources
Product: github.comAdvisory: GHSA-jw9c-mfg7-9rx2
Status: Confirmed
CVE: CVE-2024-45409 (🔍)
GCVE (CVE): GCVE-0-2024-45409
GCVE (VulDB): GCVE-100-277107
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/11/2024 06:12Updated: 11/12/2024 01:31
Changes: 09/11/2024 06:12 (67), 09/12/2024 08:18 (1), 09/20/2024 17:10 (11), 09/23/2024 09:20 (1), 10/07/2024 17:47 (10), 11/12/2024 01:31 (2)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
I noticed you added the cpe gitlab:gitlab, could you kindly verify the push of your API instance?
Best Regards,
TEAM CERT
Want to stay up to date on a daily basis?
Enable the mail alert feature now!