CVE-2017-12973 — nimbus-jose-jwt
LOWCVE-2017-12973 is a low-severity (CVSS 3.1) CWE-354 vulnerability in com.nimbusds:nimbus-jose-jwt. A fix is available for com.nimbusds:nimbus-jose-jwt — see the affected versions and patch details below.
Nimbus JOSE+JWT vulnerable to padding oracle attack
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.nimbusds:nimbus-jose-jwtReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Nimbus JOSE+JWT before 4.39 proceeds improperly after detection of an invalid HMAC in authenticated AES-CBC decryption, which allows attackers to conduct a padding oracle attack.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.nimbusds:nimbus-jose-jwt | all versions | 4.39com.nimbusds:nimbus-jose-jwt:4.39 |
Affected Products
nimbus jose\+jwtconnect2idDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.nimbusds:nimbus-jose-jwt, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.nimbusds:nimbus-jose-jwt to 4.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-12973 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2017-12973 in your dependencies?
Find it across Maven, including transitive dependencies.