CVE-2025-25292CWE-347CWE-436

Ruby SAML vulnerable to SAML authentication bypass due to namespace handling (parser differential)

Critical · published March 12, 2025

Patch now

High probability of exploitation

CVSS calls it critical at 9.3. It sits in the 99.3th percentile for exploit probability.

CVSS v4.0
9.3
EPSS
65%
Percentile
99.3
In the wild
Unconfirmed
What it is

🚨 An authentication bypass vulnerability lurks in ruby-saml, making it easier for an attacker to sneak past your defenses! 🔥 Think of this like a restaurant with two chefs, each interpreting the same recipe differently. One chef produces a dish that meets health standards, while the other creates something that even the health inspector wouldn't approve of—allowing the inspectors to miss crucial steps! An attacker could exploit this differential parsing to perform a Signature Wrapping attack, effectively bypassing authentication controls. Imagine a malicious actor slipping through security like a ghost, gaining unauthorized access to sensitive user information or even compromising entire accounts. The risk is absolutely devastating!

Put simply

Think of this like a restaurant with two chefs, each interpreting the same recipe differently. One chef produces a dish that meets health standards, while the other creates something that even the health inspector wouldn't approve of—allowing the inspectors to miss crucial steps! This vulnerability arises because ruby-saml relies on two different XML parsers—ReXML and Nokogiri—which can produce conflicting document structures from the same input. This inconsistency enables attackers to manipulate the authentication process and bypass security checks altogether.

What to do

An attacker could exploit this differential parsing to perform a Signature Wrapping attack, effectively bypassing authentication controls. Imagine a malicious actor slipping through security like a ghost, gaining unauthorized access to sensitive user information or even compromising entire accounts. The risk is absolutely devastating! To protect your application, upgrade to ruby-saml version 1.12.4 or 1.18.0 immediately. Ensure that your XML parsing is consistent and consider implementing additional security measures, such as stricter validation on incoming XML data. You've got this! Follow these steps, and you'll patch up your defenses in no time! 🛡️

The record
Technical detail
CVSS v4.0
9.3 · CRITICAL
Vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N
EPSS
0.65086 · 99.3th percentile
Weaknesses
CWE-347 · Improper Verification of Cryptographic Signature; CWE-436 · Interpretation Conflict
Published
2025-03-12T20:53Z
EPSS history
Timeline
  • 12 MAR 20:53Z
    Ruby SAML vulnerable to SAML authentication bypass due to namespace handling (parser differential)
    cvelistv5