CVE-2023-31582

jose4j before v0.9.3 allows attackers to set a low iteration count of 1000 or less.

Published: 2023-10-25 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-31582 is rated Moderate Risk (46.5/100): CVSS High severity, with low exploitation likelihood (EPSS 0.64%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-31582

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.18% 0.64% +0.46%
2 2025-03-30 0.46% 0.18% -0.28%
3 2025-03-29 — 0.46% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-31582

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]

Weakness enumeration for CVE-2023-31582

GitHub Security Advisory for CVE-2023-31582

GHSA-7g24-qg88-p43q · Severity: high · Ecosystem: maven — jose4j uses weak cryptographic algorithm

OS Trackers for CVE-2023-31582

vendor priority summary link
debian not yet assigned CVE-2023-31582 not yet assigned priority: Debian including 1 source packages (libjose4j-java), 3 status rows across 3 suites (forky, sid, trixie): resolved 3. https://security-tracker.debian.org/tracker/CVE-2023-31582
redhat medium — https://access.redhat.com/security/cve/CVE-2023-31582
suse medium — https://www.suse.com/security/cve/CVE-2023-31582/
ubuntu medium CVE-2023-31582 medium priority: Ubuntu including 1 source packages (libjose4j-java), 12 status rows across 12 suites (bionic, focal, jammy, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 7, needs-triage 4, DNE 1. https://ubuntu.com/security/CVE-2023-31582

Affected software / configurations for CVE-2023-31582

Vendor Product Version Raw CPE
jose4j_project jose4j < 0.9.3 cpe:2.3:a:jose4j_project:jose4j:*:*:*:*:*:*:*:*

References for CVE-2023-31582

cvelogic Threat Intelligence