CVE-2017-11429 — saml2-js
HIGHCVE-2017-11429 is a high-severity (CVSS 7.7) Improper Authentication vulnerability in saml2-js. 1 public exploit reference exists, so weaponization risk is real. A fix is available for saml2-js — see the affected versions and patch details below.
Authentication bypass via incorrect XML canonicalization and DOM traversal in saml2-js
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2017-11429 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
saml2-jsnpmDescription
Versions of saml2-js prior to 1.12.4 or 2.0.2 are vulnerable to authentication bypass.
The saml2-js library 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.
Security Assertion Markup Language (SAML) is an XML-based markup language for security assertions regarding authentication and permissions, most commonly used for single sign-on (SSO) services.
Some XML DOM traversal and canonicalization APIs may be inconsistent in handling of comments within XML nodes. Incorrect use of these APIs by some SAML libraries results in incorrect parsing of the inner text of XML nodes such that any inner text after the comment is lost prior to cryptographically signing the SAML message. Text after the comment therefore has no impact on the signature on the SAML message.
A remote attacker can modify SAML content for a SAML service provider without invalidating the cryptographic signature, which may allow attackers to bypass primary authentication for the affected SAML service provider
Recommendation
If you use 1.x upgrade to version 1.12.4 or greater If you use 2.x upgrade to version 2.02 or greater
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | saml2-js | all versions | 1.12.4npm install saml2-js@1.12.4 |
| 📦npm | saml2-js | ≥ 2.0.0&&< 2.0.2 | 2.0.2npm install saml2-js@2.0.2 |
Affected Products
saml2-jscleverResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for saml2-js, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update saml2-js to 1.12.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-11429 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2017-11429 in your dependencies?
Find it across npm, including transitive dependencies.