CVE-2017-11429: Clever saml2-js 2.0 and earlier may incorrectly utilize the results of XML DOM traversal and canonicalization

Q: How do I fix CVE-2017-11429?

saml2-js: upgrade to newer than 2.0. Exact commands for each OS are on this page.

Q: Is CVE-2017-11429 being exploited?

CVE-2017-11429 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2017-11429 affect?

CVE-2017-11429 affects saml2-js. Severity is high (CVSS 7.7). Clever saml2-js 2.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, allo

Q: How urgent is CVE-2017-11429?

Priority 53/100. High severity; Public exploit reference

This month

HIGH 7.7UPGRADE

CVE-2017-11429 is a high-severity flaw (CVSS 7.7) affecting saml2-js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Clever saml2-js 2.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.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.7 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	2.7% (top 14%)
CISA exploited list	No
Weakness	CWE-287
Published	2019-04-17
Last modified	2026-06-17

Publisher (CNA): Duo Security, Inc. · Vendor: clever

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2019-04-17 14:29 UTCPublished CVE record published
2026-06-17 01:01 UTCUpdated Record last modified

clever saml2-js UPGRADE

Affected: <= 2.0

Fixed in: newer than 2.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy saml2-js || rpm -q saml2-js || saml2-js --version

2. UPGRADE to newer than 2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade saml2-js

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade saml2-js

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-11429?

saml2-js: upgrade to newer than 2.0. Exact commands for each OS are on this page.

Is CVE-2017-11429 being exploited?

CVE-2017-11429 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-11429 affect?

CVE-2017-11429 affects saml2-js. Severity is high (CVSS 7.7). Clever saml2-js 2.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, allo

How urgent is CVE-2017-11429?

Priority 53/100. High severity; Public exploit reference

References

← Back to latest CVEs