Node-SAML Contains SAML Signature Verification Vulnerability
node-saml
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| @node-saml/node-saml npm |
|
|
| passport-saml npm |
| No fix yet |
| @node-saml/passport-saml npm |
|
node-saml
| Product | Affected | Fixed in |
|---|---|---|
| @node-saml/node-saml npm |
|
|
| passport-saml npm |
| No fix yet |
| @node-saml/passport-saml npm |
|
|
A SAML library not dependent on any frameworks that runs in Node. In version 5.0.1, Node-SAML loads the assertion from the (unsigned) original response document. This is different than the parts that are verified when checking signature. This allows an attacker to modify authentication details within a valid SAML assertion. For example, in one attack it is possible to remove any character from the SAML assertion username. To conduct the attack an attacker would need a validly signed document from the identity provider (IdP). This is fixed in version 5.1.0.
From the CVE record · GitHub_M
Node-SAML can load authentication details from an unsigned response document rather than the content verified by its signature check. An attacker with a validly signed document from the identity provider can modify authentication details in the assertion, including removing characters from a username.
Check deployments using npm @node-saml/node-saml before 5.1.0, @node-saml/passport-saml before 5.1.0, or passport-saml through 3.2.4.