# GHSA-4rr6-gf59-ggw5: namshi/jose - Verification bypass

> Attackers can bypass JWT verification using asymmetric keys, allowing unauthorized access to protected resources.

- **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:** 17 May 2024

## What is GHSA-4rr6-gf59-ggw5?

GHSA-4rr6-gf59-ggw5 is an authentication bypass vulnerability in namshi/jose, published on 17 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Several widely-used JSON Web Token (JWT) libraries, including node-jsonwebtoken, pyjwt, namshi/jose, php-jwt, and jsjwt, are affected by critical vulnerabilities that could allow attackers to bypass the verification step when using asymmetric keys (RS256, RS384, RS512, ES256, ES384, ES512).

## Which versions are affected by GHSA-4rr6-gf59-ggw5?

2 open source packages ship an affected version, including namshi/jose.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `namshi/jose` | Packagist | All versions | 2.2.0 |
| `namshi/jose` | Packagist | All versions | 2.2.0 |

## How do I fix GHSA-4rr6-gf59-ggw5?

Upgrade namshi/jose to 2.2.0 or later.

## Is GHSA-4rr6-gf59-ggw5 being exploited?

There is no known exploitation of GHSA-4rr6-gf59-ggw5 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-4rr6-gf59-ggw5 and fix it if it is affected.

What it is: GHSA-4rr6-gf59-ggw5 is an authentication bypass vulnerability in namshi/jose, published on 17 May 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-4rr6-gf59-ggw5 in the wild and no public exploit code.

Affected packages and fixed versions:
- namshi/jose (Packagist): affected all versions; fixed in 2.2.0
- namshi/jose (Packagist): affected all versions; fixed in 2.2.0

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-4rr6-gf59-ggw5/ (Markdown: https://insights.sbomify.com/GHSA-4rr6-gf59-ggw5/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-4rr6-gf59-ggw5

---
From sbomify Insights: https://insights.sbomify.com/GHSA-4rr6-gf59-ggw5/
Summaries are generated and may contain mistakes; the official description above is the record.