@node-saml/node-saml 4.0.0-beta.3 vulnerabilities

Known vulnerabilities in the @node-saml/node-saml package. This does not include vulnerabilities belonging to this package’s dependencies.

Vulnerability	Vulnerable Version
M Access Control Bypass @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 `LogoutRequest` XML to be reused multiple times even when the current time is past the `NotOnOrAfter`. How to fix Access Control Bypass? Upgrade `@node-saml/node-saml` to version 4.0.5 or higher.	<4.0.5
H Improper Verification of Cryptographic Signature @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 `passport-sam`l. 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 `@node-saml/node-saml` to version 4.0.0-beta.5 or higher.	<4.0.0-beta.5
H Improper Verification of Cryptographic Signature @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 `passport-saml`. 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 `@node-saml/node-saml` to version 4.0.0-beta.5 or higher.	<4.0.0-beta.5

Vulnerability

Vulnerable Version

Access Control Bypass

@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 LogoutRequest XML to be reused multiple times even when the current time is past the NotOnOrAfter.

How to fix Access Control Bypass?

Upgrade @node-saml/node-saml to version 4.0.5 or higher.

<4.0.5

Improper Verification of Cryptographic Signature

@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 passport-saml.

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 @node-saml/node-saml to version 4.0.0-beta.5 or higher.

<4.0.0-beta.5

Improper Verification of Cryptographic Signature

@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 passport-saml.

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 @node-saml/node-saml to version 4.0.0-beta.5 or higher.

<4.0.0-beta.5

@node-saml/node-saml@4.0.0-beta.3 vulnerabilities

SAML 2.0 implementation for Node.js

latest version

latest non vulnerable version

first published

latest version published

licenses detected

Direct Vulnerabilities

How to fix?