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

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
Low
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.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.106%
(44th percentile)

Weaknesses

CVE ID

CVE-2017-1000452

GHSA ID

GHSA-8jjf-w7j6-323c

Source code

Credits

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