Samlify vulnerable to Authentication Bypass by allowing tokens to be reused with different usernames
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
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2017-1000452US | high7.5 | — | ||
An XML Signature Wrapping vulnerability exists in Samlify 2.2.0 and earlier, and in predecessor Express-saml2 which could allow attackers to impersonate arbitrary users. | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/tngan/samlifyPACKAGE
- https://github.com/tngan/samlify/commit/d382bbc7c6b8ea889839ae1f178730c25b09eb42WEB
- https://github.com/tngan/samlify/compare/v2.4.0-rc4...v2.4.0-rc5WEB
- https://github.com/tngan/samlify/releases/tag/v2.4.0-rc5WEB
- https://hackerone.com/reports/356284WEB
- https://nvd.nist.gov/vuln/detail/CVE-2017-1000452ADVISORY
- https://www.whitehats.nl/blog/xml-signature-wrapping-samlifyWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan