Skip to content

Samlify vulnerable to Authentication Bypass by allowing tokens to be reused with different usernames

High severity GitHub Reviewed Published Jan 4, 2018 to the GitHub Advisory Database • Updated Aug 18, 2023

Package

npm samlify (npm)

Affected versions

< 2.4.0-rc5

Patched versions

2.4.0-rc5

Description

Versions of samlify prior to 2.4.0-rc5 are vulnerable to Authentication Bypass. The package fails to prevent XML Signature Wrapping, allowing tokens to be reused with different usernames. A remote attacker can modify SAML content for a SAML service provider without invalidating the cryptographic signature, which may allow attackers to bypass primary authentication for the affected SAML service provider.

Recommendation

Upgrade to version 2.4.0-rc5 or later

References

Published to the GitHub Advisory Database Jan 4, 2018
Reviewed Jun 16, 2020
Last updated Aug 18, 2023

Severity

High
7.5
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

CVE ID

CVE-2017-1000452

GHSA ID

GHSA-8jjf-w7j6-323c

Source code

Credits

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