Name | CVE-2017-11430 |
Description | OmniAuth OmnitAuth-SAML 1.9.0 and earlier may incorrectly utilize the results of XML DOM traversal and canonicalization APIs in such a way that an attacker may be able to manipulate the SAML data without invalidating the cryptographic signature, allowing the attack to potentially bypass authentication to SAML service providers. |
Source | CVE (at NVD; CERT, LWN, oss-sec, fulldisc, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more) |
Vulnerable and fixed packages
The table below lists information on source packages.
Source Package | Release | Version | Status |
---|
ruby-omniauth-saml (PTS) | bullseye | 1.10.0-1 | fixed |
| bookworm | 2.1.0-2 | fixed |
| sid, trixie | 2.2.1-1 | fixed |
The information below is based on the following data on fixed versions.
Package | Type | Release | Fixed Version | Urgency | Origin | Debian Bugs |
---|
ruby-omniauth-saml | source | (unstable) | (not affected) | | | |
Notes
- ruby-omniauth-saml <not-affected> (The actual vulnerability is in ruby-saml, which is used by the Debian package)
The change in 1.10.0 simply bumps the version requirement
https://github.com/omniauth/omniauth-saml/issues/156
https://github.com/omniauth/omniauth-saml/pull/157
https://duo.com/blog/duo-finds-saml-vulnerabilities-affecting-multiple-implementations
https://www.kb.cert.org/vuls/id/475445