Signature bypass via multiple root elements in Passport-SAML
node-saml passport-saml
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| passport-saml npm |
|
|
| node-saml npm |
|
|
| @node-saml/node-saml npm |
node-saml passport-saml
| Product | Affected | Fixed in |
|---|---|---|
| passport-saml npm |
|
|
| node-saml npm |
|
|
| @node-saml/node-saml npm |
< 4.0.0-beta.5
|
| @node-saml/passport-saml npm |
|
|
Passport-SAML is a SAML 2.0 authentication provider for Passport, the Node.js authentication library. A remote attacker may be able to bypass SAML authentication on a website using passport-saml. 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. Users should upgrade to passport-saml version 3.2.2 or newer. The issue was also present in the beta releases of `node-saml` before version 4.0.0-beta.5. If you cannot upgrade, disabling SAML authentication may be done as a workaround.
From the CVE record · GitHub_M
Affected passport-saml and node-saml packages may allow a remote attacker to bypass SAML authentication. The attacker must possess an arbitrary IDP-signed XML element; depending on the IDP, an attack without a valid user may also be possible if the attacker can trigger generation of a signed message.
Check websites using npm passport-saml before 3.2.2, node-saml or @node-saml/node-saml before 4.0.0-beta.5, or @node-saml/passport-saml before 4.0.0-beta.3.