CVE-2024-31033
mediumpriority · track · 0OT risk · elevatedEPSS 0.008 · 55 %ileDEEUUSEPSS · scored 2026-10-23
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (6)
Products and version ranges known to be affected.
- IBM Business Automation Workflow 22.0.2all versionscert_bundDEcpe:/a:ibm:business_automation_workflow:22.0.2
- IBM Business Automation Workflow 23.0.1all versionscert_bundDEcpe:/a:ibm:business_automation_workflow:23.0.1
- IBM Business Automation Workflow 23.0.2all versionscert_bundDEcpe:/a:ibm:business_automation_workflow:23.0.2
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2024-1273IBM Business Automation Workflow: Schwachstelle ermöglicht nicht spezifizierten AngriffDeutsch2024-06-02csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann eine Schwachstelle in IBM Business Automation Workflow ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen.
- GHSA-r65j-6h5f-4f92Withdrawn: JJWT improperly generates signing keys2024-04-01ghsa · osvUS
## Withdrawn Advisory This advisory has been withdrawn because it has been found to be disputed. Please see the issue [here](https://github.com/jwtk/jjwt/issues/930#issuecomment-2032699358) for more information. ## Original 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.
also known as (3)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (12)
External citations — patches, advisories, analysis.
- https://cxsecurity.com/cveshow/CVE-2024-31033/cnnvd
- https://github.com/2308652512/JJWT_BUGcnnvd
- https://github.com/jwtk/jjwt/issues/930#issuecomment-2032699358cnnvd
- https://www.viralpatel.net/java-create-validate-jwt-token/cnnvd
- https://github.com/2308652512/JJWT_BUGenisa_euvd
- https://github.com/jwtk/jjwtenisa_euvd
- https://github.com/jwtk/jjwt/issues/930#issuecomment-2032699358enisa_euvd
- https://www.viralpatel.net/java-create-validate-jwt-token/enisa_euvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan