@node-saml/node-saml@4.0.0-beta.4 vulnerabilities
SAML 2.0 implementation for Node.js
-
latest version
5.0.0
-
latest non vulnerable version
-
first published
2 years ago
-
latest version published
3 months ago
-
licenses detected
- >=0
Direct Vulnerabilities
Known vulnerabilities in the @node-saml/node-saml package. This does not include vulnerabilities belonging to this package’s dependencies.
Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.| Vulnerability | Vulnerable Version |
|---|---|
@node-saml/node-saml is a SAML 2.0 implementation for Node.js Affected versions of this package are vulnerable to Access Control Bypass. The lack of checking of the current timestamp allows a How to fix Access Control Bypass? Upgrade |
<4.0.5
|
@node-saml/node-saml is a SAML 2.0 implementation for Node.js Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature by allowing a remote attacker to bypass SAML authentication on a website using Note A successful attack requires that the attacker is in possession of an arbitrary IDP signed XML element. Depending on the IDP used, fully unauthenticated attacks (e.g without access to a valid user) might also be feasible if generation of a signed message can be triggered. How to fix Improper Verification of Cryptographic Signature? Upgrade |
<4.0.0-beta.5
|
@node-saml/node-saml is a SAML 2.0 implementation for Node.js Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature by allowing a remote attacker to bypass SAML authentication on a website using Note A successful attack requires that the attacker is in possession of an arbitrary IDP-signed XML element. Depending on the IDP used, fully unauthenticated attacks (e.g, without access to a valid user) might also be feasible if the generation of a signed message can be triggered. How to fix Improper Verification of Cryptographic Signature? Upgrade |
<4.0.0-beta.5
|