Skip to content
Fencer Intel
high —

GHSA-5wrg-8fxp-cx9r json

passport-wsfed-saml2 Signature Bypass vulnerability

published 3y ago modified 3y ago

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

## Information Please note that this is not a new disclosure, and is previously reported in our [SECURITY-NOTICE.md](https://github.com/auth0/passport-wsfed-saml2/commit/520b9fc0bb4249ce83bec47e30153419f086ab70 ) which we removed in favor of github advisory.

# Overview

A vulnerability was found in the validation of a SAML signature. The validation doesn't ensure that the "Signature" tag is at the proper location inside an "Assertion" tag. This leads to a signature relocation attack where the attacker can corrupt one field of data while maintaining the signature valid. This could allow an authenticated attacker to "remove" one group from the assertion or corrupt another field of an assertion.

# Am I affected?

You are affected if you are using the passport-wsfed-saml2 library to version < 3.0.10

# How do I fix it?

You may fix this issue by upgrading passport-wsfed-saml2 library to version 3.0.10 or above.

# Will the fix impact my users?

This fix patches the library that your application runs, but will not impact your users, their current state, or any existing sessions.

Patch / fix

  • npm passport-wsfed-saml2 3.0.10

Is GHSA-5wrg-8fxp-cx9r in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
npm passport-wsfed-saml2
<3.0.10
3.0.10

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.