Skip to content

Signature bypass via multiple root elements

High severity GitHub Reviewed Published Oct 11, 2022 in node-saml/passport-saml • Updated Jan 27, 2023

Package

npm @node-saml/node-saml (npm)

Affected versions

< 4.0.0-beta.5

Patched versions

4.0.0-beta.5
npm @node-saml/passport-saml (npm)
< 4.0.0-beta.3
4.0.0-beta.3
npm node-saml (npm)
< 4.0.0-beta.5
4.0.0-beta.5
npm passport-saml (npm)
< 3.2.2
3.2.2

Description

Impact

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.

Patches

Users should upgrade to passport-saml 3.2.2 or newer. The issue was also present in the beta releases of node-saml before v4.0.0-beta.5.

Workarounds

Disable SAML authentication.

References

Are there any links users can visit to find out more?

For more information

If you have any questions or comments about this advisory:

Credits

  • Felix Wilhelm of Google Project Zero

References

@cjbarth cjbarth published to node-saml/passport-saml Oct 11, 2022
Published by the National Vulnerability Database Oct 12, 2022
Published to the GitHub Advisory Database Oct 12, 2022
Reviewed Oct 12, 2022
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

1.452%
(86th percentile)

Weaknesses

CVE ID

CVE-2022-39299

GHSA ID

GHSA-m974-647v-whv7

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.