Skip to content
Fencer Intel
critical —

GHSA-hw46-3hmr-x9xv json

omniauth-saml has dependency on ruby-saml version with Signature Wrapping Attack issue

published last yr. modified 9mo ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Summary There are 2 new Critical Signature Wrapping Vulnerabilities (CVE-2025-25292, CVE-2025-25291) and a potential DDOS Moderated Vulneratiblity (CVE-2025-25293) affecting ruby-saml, a dependency of omniauth-saml.

The fix will be applied to ruby-saml and released 12 March 2025, under version 1.18.0.

Please [upgrade](https://github.com/omniauth/omniauth-saml/blob/master/omniauth-saml.gemspec#L16) the ruby-saml requirement to v1.18.0.

### Impact Signature Wrapping Vulnerabilities allows an attacker to impersonate a user.

Patch / fix

  • rubygems omniauth-saml 1.10.6, 2.1.3, 2.2.3

Is GHSA-hw46-3hmr-x9xv in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
rubygems omniauth-saml
>=2.2.0, <2.2.3
>=2.0.0, <2.1.3
<1.10.6
2.2.3
2.1.3
1.10.6

Classification

Weakness
  • CWE-347 Improper Verification of Cryptographic Signature

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.