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

GHSA-9wmf-xf3h-r8pr — jberet-core

MEDIUMFix: jberet/jsr352@eeef999

GHSA-9wmf-xf3h-r8pr is a medium-severity (CVSS 6.5) CWE-523 vulnerability in org.jberet:jberet-core. A fix is available for org.jberet:jberet-core — see the affected versions and patch details below.

Jberet: jberet-core logging database credentials

Also known asCVE-2024-1102
Published
Apr 25, 2024
Updated
Oct 24, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 26, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • 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 GHSA-9wmf-xf3h-r8pr.

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs54th percentile — riskier than 54% 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

GHSA-9wmf-xf3h-r8pr 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 379,145 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.jberet:jberet-core

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

A vulnerability was found in jberet-core logging. An exception in 'dbProperties' might display user credentials such as the username and password for the database-connection.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.jberet:jberet-coreall versions2.2.1.Finalorg.jberet:jberet-core:2.2.1.Final

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.jberet:jberet-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update org.jberet:jberet-core to 2.2.1.Final or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9wmf-xf3h-r8pr 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 GHSA-9wmf-xf3h-r8pr can be triaged on real exposure rather than presence alone.

Tailored to GHSA-9wmf-xf3h-r8pr. 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
Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for GHSA-9wmf-xf3h-r8pr (CC BY 4.0)
ProductFixed inAdvisory
Red Hat JBoss Enterprise Application Platformorg.jberet/jberet-core:1.3.9.SP3-redhat-00001RHSA-2024:1677
Red Hat JBoss Enterprise Application Platform 8jberet-coreRHSA-2024:3583
Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 8eap8-hibernate-search-0:6.2.2-1.Final_redhat_00001.1.el8eapRHSA-2024:3580
Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 9eap8-hibernate-search-0:6.2.2-1.Final_redhat_00001.1.el9eapRHSA-2024:3581

Frequently Asked Questions

A vulnerability was found in jberet-core logging. An exception in 'dbProperties' might display user credentials such as the username and password for the database-connection.
O3 Security · Impact-Aware SCA

Is GHSA-9wmf-xf3h-r8pr in your dependencies?

O3 Security finds GHSA-9wmf-xf3h-r8pr across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-9wmf-xf3h-r8pr: jberet-core | O3 Security