# CVE-2024-31033: Weak cryptography in n/a

> JJWT library may allow weak keys due to ignored characters, potentially leading to security bypass if users misconfigure key strength.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Apr 2024
- **Updated:** 27 Aug 2024

## What is CVE-2024-31033?

CVE-2024-31033 is a medium-severity vulnerability in n/a, published on 1 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

JJWT (aka Java JWT) through 0.12.5 ignores certain characters and thus a user might falsely conclude that they have a strong key. The impacted code is the setSigningKey() method within the DefaultJwtParser class and the signWith() method within the DefaultJwtBuilder class. NOTE: the vendor disputes this because the "ignores" behavior cannot occur (in any version) unless there is a user error in how JJWT is used, and because the version that was actually tested must have been more than six years out of date.

## Which versions are affected by CVE-2024-31033?


## How do I fix CVE-2024-31033?

No fix has been published for CVE-2024-31033 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-31033 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31033 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-31033 and fix it if it is affected.

What it is: CVE-2024-31033 is a medium-severity vulnerability in n/a, published on 1 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31033 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2024-31033/ (Markdown: https://insights.sbomify.com/CVE-2024-31033/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-31033
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-31033
- OSV: https://osv.dev/vulnerability/CVE-2024-31033

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-31033/
Summaries are generated and may contain mistakes; the official description above is the record.