Skip to content
Fencer Intel
high 7.7

CVE-2017-11428 json

Multiple SAML libraries may allow authentication bypass via incorrect XML canonicalization and DOM traversal

published 2019-04-17 7 y ago modified 2026-06-17 4 mo ago also GHSA-x2fr-v8wf-8wwv , EUVD-2019-0609

cvss
7.7
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.5%
EPSS 2.5% chance of exploitation in 30 days, percentile 84%
public exploits
0
none known

Summary

OneLogin Ruby-SAML 1.6.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.

Patch / fix

  • rubygems ruby-saml 1.7.0
  • OneLogin Ruby-SAML 1.6.0
  • ruby-saml Debian 12 1.7.2-1

debian advisories DEBIAN-CVE-2017-11428

  • ruby-saml Ubuntu Pro 16.04 LTS 1.1.2-1ubuntu1+esm1

ubuntu advisories UBUNTU-CVE-2017-11428

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Exploit prediction

2.46% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • duo.com https://duo.com/blog/duo-finds-saml-vulnerabilities-affecting-multiple-implementations referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 7.7 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 7.7 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
rubygems ruby-saml
<1.7.0
1.7.0

Affected products

  • OneLogin Ruby-SAML

Classification

Weakness

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.