Skip to content
Fencer Intel
critical 10.0

GHSA-cvp8-5r8g-fhvq json

omniauth-saml vulnerable to Improper Verification of Cryptographic Signature

published 2y ago modified 3mo ago

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

Summary

ruby-saml, the dependent SAML gem of omniauth-saml has a signature wrapping vulnerability in <= v1.12.0 and v1.13.0 to v1.16.0 , see https://github.com/SAML-Toolkits/ruby-saml/security/advisories/GHSA-jw9c-mfg7-9rx2 As a result, omniauth-saml created a [new release](https://github.com/omniauth/omniauth-saml/releases) by upgrading ruby-saml to the patched versions v1.17.

Patch / fix

  • rubygems omniauth-saml 1.10.5, 2.1.2, 2.2.1

Is GHSA-cvp8-5r8g-fhvq 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

CVSS scores

assigned by version score vector
GitHub 3.1 10.0 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
rubygems omniauth-saml
>=2.0.0, <2.1.2
<1.10.5
>=2.2.0, <2.2.1
2.1.2
1.10.5
2.2.1

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.