CVE-2023-31582 — jose4j
HIGHCVE-2023-31582 is a high-severity (CVSS 7.5) CWE-331 vulnerability in org.bitbucket.b_c:jose4j. A fix is available for org.bitbucket.b_c:jose4j — see the affected versions and patch details below.
jose4j uses weak cryptographic algorithm
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-31582.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2023-31582 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.bitbucket.b_c:jose4jReal-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
jose4j before v0.9.3 allows attackers to set a low PBES2 iteration count of 1000 or less.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.bitbucket.b_c:jose4j | all versions | 0.9.3org.bitbucket.b_c:jose4j:0.9.3 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.bitbucket.b_c:jose4j, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.bitbucket.b_c:jose4j to 0.9.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-31582 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-31582 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-31582. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This flaw would require manually setting of the number of iterations under 1000 for Json Web Encryption, therefore, a malicious user would need previous access to modify it. Also, a user would still be able to set the variable incorrectly and make the environment less secure for JWE. This is currently rated as a…
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat AMQ Streams 2.6.0 | jose4j | RHSA-2023:7678 |
| Red Hat build of Quarkus 2.13.9.Final | org.bitbucket.b_c/jose4j:0.9.3.redhat-00004 | RHSA-2023:7700 |
| Red Hat Data Grid 8.4.6 | jose4j | RHSA-2023:7676 |
Frequently Asked Questions
Is CVE-2023-31582 in your dependencies?
O3 Security finds CVE-2023-31582 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.