# GHSA-mfcp-34xw-p57x: Authentication Bypass in saml2-js

> Attackers can bypass authentication by reusing encrypted SAML assertion tokens due to missing condition enforcement in saml2-js.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Sep 2020

## What is GHSA-mfcp-34xw-p57x?

GHSA-mfcp-34xw-p57x is an authentication bypass vulnerability in saml2-js, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Versions of `saml2-js` prior to 2.0.5 are vulnerable to an Authentication Bypass. The package fails to enforce the assertion conditions for encrypted assertions, which may allow an attacker to reuse encrypted assertion tokens indefinitely.

## Recommendation

Upgrade to version 2.0.5 or later.

## Which versions are affected by GHSA-mfcp-34xw-p57x?

2 open source packages ship an affected version, including saml2-js.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `saml2-js` | npm | All versions | 2.0.5 |
| `saml2-js` | npm | All versions | 2.0.5 |

## How do I fix GHSA-mfcp-34xw-p57x?

Upgrade saml2-js to 2.0.5 or later.

## Is GHSA-mfcp-34xw-p57x being exploited?

There is no known exploitation of GHSA-mfcp-34xw-p57x in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-mfcp-34xw-p57x and fix it if it is affected.

What it is: GHSA-mfcp-34xw-p57x is an authentication bypass vulnerability in saml2-js, published on 3 Sep 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-mfcp-34xw-p57x in the wild and no public exploit code.

Affected packages and fixed versions:
- saml2-js (npm): affected all versions; fixed in 2.0.5
- saml2-js (npm): affected all versions; fixed in 2.0.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-mfcp-34xw-p57x/ (Markdown: https://insights.sbomify.com/GHSA-mfcp-34xw-p57x/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-mfcp-34xw-p57x

---
From sbomify Insights: https://insights.sbomify.com/GHSA-mfcp-34xw-p57x/
Summaries are generated and may contain mistakes; the official description above is the record.