Vulnerability Database · npm · saml2-js · Version
saml2-js 0.3.0
0.3.0 is affected by 2 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 4.0.4.
Critical 0 High 0 Medium 2 Low 0 Unrated 0
-
Released 16 Oct 2014
Licence Apache-2.0
Also known from other sources 2
Newer releases 62
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
saml2-js 0.3.0 vulnerabilities
2 vulnerabilities cover saml2-js 0.3.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2017-11429: Authentication bypass via incorrect XML canonicalization and DOM traversal in saml2-js | 7.7 medium | 1.12.4 | 05 Jul 2019 |
| Authentication Bypass in saml2-js | 6.8 medium | 2.0.5 | 03 Sep 2020 |
Looking for another version, or everything Vulert holds for saml2-js?
Questions
About saml2-js 0.3.0
Is saml2-js 0.3.0 vulnerable?
Yes. 2 vulnerabilities in the Vulert database cover saml2-js 0.3.0: 0 critical, 0 high, 2 medium and 0 low. The upgrade Vulert recommends is 4.0.4, and each entry above names the fixed version to move to.
Which version of saml2-js should I use instead of 0.3.0?
4.0.4 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.3.0 the latest release of saml2-js?
No. 0.3.0 was published 16 Oct 2014, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor saml2-js for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the saml2-js version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.