Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
5 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
This vulnerability allows an attacker to impersonate any user during SAML authentication by tampering with a valid SAML response. This can be done by adding attributes to the response. Am I Affected? You are affected by this SAML Attribute Smuggling vulnerability if you are using passport-wsfed-saml2 version 4.6.3 or below, specifically under the following conditions: 1. The service provider is using passport-wsfed-saml2, 2. A valid SAML Response signed by the Identity Provider can be obtained Fix Upgrade to v4.6.4 or greater.
Recommended action: Upgrade to 4.6.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
This vulnerability allows an attacker to impersonate any user during SAML authentication by crafting a SAMLResponse. This can be done by using a valid SAML object that was signed by the configured IdP. Am I Affected? You are affected by this SAML Signature Wrapping vulnerability if you are using passport-wsfed-saml2 version 4.6.3 or below, specifically under the following conditions: 1. The service provider is using passport-wsfed-saml2, 2. A valid SAML document signed by the Identity Provider can be obtained. Fix Upgrade to v4.6.4 or greater.
Recommended action: Upgrade to 4.6.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Information Please note that this is not a new disclosure, and is previously reported in our SECURITY-NOTICE.md 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.
Recommended action: Upgrade to 3.0.10 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Information Please note that this is not a new disclosure, and is previously reported in our SECURITY-NOTICE.md which we removed in favor of github advisory. Overview This vulnerability allows an attacker to impersonate another user and potentially elevate their privileges if the SAML identity provider: - signs SAML response and signs assertion - does not sign SAML response and signs assertion Am I affected? You may be affected if you use SAML2 protocol with passport-wsfed-saml2 versions below 3.0.5 and your SAML identity Provider: 1. signs SAML response and signs assertion; or 2. does not sign SAML response and signs assertion How do I fix it? You may fix this vulnerability by upgrading your library to version 3.0.5 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.
Recommended action: Upgrade to 3.0.5 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
A remote attacker can bypass WSFed authentication on a website using passport-wsfed-saml2. A successful attack requires that the attacker is in possession of an arbitrary IDP signed WSFed assertion. 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. Am I affected? You are affected if you are using WSFed protocol with the passport-wsfed-saml2 library versions < 4.6.3. SAML2 protocol is not affected. How do I fix it? Upgrade the library to version 4.6.3. Will the fix impact my users? No, the fix will not impact your users.
Recommended action: Upgrade to 4.6.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.