# GHSA-rcm4-jv5g-wccm: zfr authentication adapter did not verify validity of tokens

> An authentication adapter failed to verify token validity, allowing attackers to use expired tokens to bypass authentication controls.

- **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:** 7 Jun 2024

## What is GHSA-rcm4-jv5g-wccm?

GHSA-rcm4-jv5g-wccm is an authentication bypass vulnerability in zfr/zfr-oauth2-server-module, published on 7 Jun 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Previous to @2ca5bb1c2f11537be8f94ca6867d8d69789e744a (release [0.1.2](https://github.com/zf-fr/zfr-oauth2-server-module/tree/0.1.2)), tokens weren't checked for validity/expiration.

This potentially caused a security issue if expired tokens were not deleted after the expiration time was past, allowing anyone to still use invalidated authentication credentials.

## Which versions are affected by GHSA-rcm4-jv5g-wccm?

2 open source packages ship an affected version, including zfr/zfr-oauth2-server-module.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `zfr/zfr-oauth2-server-module` | Packagist | All versions | 0.1.2 |
| `zfr/zfr-oauth2-server-module` | Packagist | All versions | 0.1.2 |

## How do I fix GHSA-rcm4-jv5g-wccm?

Upgrade zfr/zfr-oauth2-server-module to 0.1.2 or later.

## Is GHSA-rcm4-jv5g-wccm being exploited?

There is no known exploitation of GHSA-rcm4-jv5g-wccm in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-rcm4-jv5g-wccm and fix it if it is affected.

What it is: GHSA-rcm4-jv5g-wccm is an authentication bypass vulnerability in zfr/zfr-oauth2-server-module, published on 7 Jun 2024. 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-rcm4-jv5g-wccm in the wild and no public exploit code.

Affected packages and fixed versions:
- zfr/zfr-oauth2-server-module (Packagist): affected all versions; fixed in 0.1.2
- zfr/zfr-oauth2-server-module (Packagist): affected all versions; fixed in 0.1.2

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-rcm4-jv5g-wccm/ (Markdown: https://insights.sbomify.com/GHSA-rcm4-jv5g-wccm/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-rcm4-jv5g-wccm

---
From sbomify Insights: https://insights.sbomify.com/GHSA-rcm4-jv5g-wccm/
Summaries are generated and may contain mistakes; the official description above is the record.