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.
Project Subscriptions
No data.
Advisories
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-r65j-6h5f-4f92 | Withdrawn: JJWT improperly generates signing keys |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
Tue, 27 Aug 2024 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-27T17:59:14.397Z
Reserved: 2024-03-27T00:00:00.000Z
Link: CVE-2024-31033
Updated: 2024-08-02T01:46:04.353Z
Status : Deferred
Published: 2024-04-01T02:15:07.850
Modified: 2026-04-15T00:35:42.020
Link: CVE-2024-31033
No data.
OpenCVE Enrichment
No data.
Weaknesses
No weakness.
Github GHSA