Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2023-51775 — jose4j

MEDIUM

CVE-2023-51775 is a medium-severity (CVSS 6.5) Uncontrolled Resource Consumption 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 denial of service via specifically crafted JWE

Also known asGHSA-6qvw-249j-h44c
Published
Feb 29, 2024
Updated
Mar 14, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2023-51775.

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

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-51775 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

1 pkg affected
☕org.bitbucket.b_c:jose4j

Real-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

The jose4j component before 0.9.4 for Java allows attackers to cause a denial of service (CPU consumption) via a large p2c (aka PBES2 Count) value.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.bitbucket.b_c:jose4jall versions0.9.4org.bitbucket.b_c:jose4j:0.9.4

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. Fix

    Update org.bitbucket.b_c:jose4j to 0.9.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-51775 is resolved across your whole dependency graph.

  3. 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.

  4. 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-51775 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2023-51775. 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.

Red HatModerate

The vulnerability in the jose4j library, where the "p2c" parameter in PBKDF2-based JWE key management algorithms can be manipulated to induce high computational consumption, is classified as moderate severity due to its potential impact on service availability and resource exhaustion. By setting a large value for…

ProductFixed inAdvisory
HawtIO 4.0.0 for Red Hat build of Apache Camel 4jose4jRHSA-2024:3550
Red Hat build of Apicurio Registry 2.6.1 GAjose4jRHSA-2024:4873
Red Hat JBoss Enterprise Application Platform 7jose4jRHSA-2024:8080
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8eap7-hal-console-0:3.3.24-1.Final_redhat_00001.1.el8eapRHSA-2024:8076
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9eap7-hal-console-0:3.3.24-1.Final_redhat_00001.1.el9eapRHSA-2024:8077
Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7eap7-hal-console-0:3.3.24-1.Final_redhat_00001.1.el7eapRHSA-2024:8075
Red Hat JBoss Enterprise Application Platform 8jose4jRHSA-2024:4392
Red Hat JBoss Enterprise Application Platform Expansion Packsee advisoryRHSA-2024:4386

Frequently Asked Questions

The jose4j component before 0.9.4 for Java allows attackers to cause a denial of service (CPU consumption) via a large p2c (aka PBES2 Count) value.
O3 Security · Impact-Aware SCA

Is CVE-2023-51775 in your dependencies?

O3 Security finds CVE-2023-51775 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2023-51775: jose4j DoS (Medium 6.5) | O3 Security