GHSA-hxhc-wmg8-xrqf namshi/jose insecure JSON Web Signatures (JWS)
Not scored
Published
Check this codebase for GHSA-hxhc-wmg8-xrqf and fix it if it is affected.
What it is: GHSA-hxhc-wmg8-xrqf 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-hxhc-wmg8-xrqf in the wild and no public exploit code.
Affected packages and fixed versions:
- namshi/jose (Packagist): affected all versions; fixed in 1.1.2
- namshi/jose (Packagist): affected all versions; fixed in 1.1.2
- namshi/jose (Packagist): affected from 1.2.0; fixed in 1.2.2
- namshi/jose (Packagist): affected from 1.2.0; fixed in 1.2.2
- namshi/jose (Packagist): affected from 2.0.0; fixed in 2.0.3
- namshi/jose (Packagist): affected from 2.0.0; fixed in 2.0.3
- namshi/jose (Packagist): affected from 2.1.0; fixed in 2.1.2
- namshi/jose (Packagist): affected from 2.1.0; fixed in 2.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-hxhc-wmg8-xrqf/ (Markdown: https://insights.sbomify.com/GHSA-hxhc-wmg8-xrqf/index.md)
Attackers can bypass authentication and impersonate users if the library is configured to accept unsecure 'none' algorithm signatures.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-hxhc-wmg8-xrqf?
GHSA-hxhc-wmg8-xrqf 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
namshi/jose allows the acceptance of unsecure JSON Web Signatures (JWS) by default. The vulnerability arises from the $allowUnsecure flag, which, when set to true during the loading of JWSes, permits tokens signed with 'none' algorithms to be processed. This behavior poses a significant security risk as it could allow an attacker to impersonate users by crafting a valid jwt token.
Which versions are affected by GHSA-hxhc-wmg8-xrqf?
8 open source packages ship an affected version, including namshi/jose.
| Package | Affected | Fixed in |
|---|---|---|
namshi/jose Packagist | All versions | 1.1.2 |
namshi/jose Packagist | All versions | 1.1.2 |
namshi/jose Packagist | From 1.2.0 | 1.2.2 |
namshi/jose Packagist | From 1.2.0 | 1.2.2 |
namshi/jose Packagist | From 2.0.0 | 2.0.3 |
namshi/jose Packagist | From 2.0.0 | 2.0.3 |
2 more packages
namshi/jose Packagist | From 2.1.0 | 2.1.2 |
namshi/jose Packagist | From 2.1.0 | 2.1.2 |
How do I fix GHSA-hxhc-wmg8-xrqf?
Upgrade namshi/jose to a fixed version for your release line: 1.1.2, 1.2.2, 2.0.3 or 2.1.2.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is GHSA-hxhc-wmg8-xrqf being exploited?
There is no known exploitation of GHSA-hxhc-wmg8-xrqf in the wild and no public exploit code.