CVE-2024-1102 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
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 CVE-2024-1102.
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
org.jberet:jberet-coreReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jberet:jberet-core | all versions | 2.2.1.Finalorg.jberet:jberet-core:2.2.1.Final |
Affected Products
jberetjberetjboss enterprise application platformredhatDetection & mitigation playbook
Open-source dependencyDetect
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.
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 CVE-2024-1102 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
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.
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 CVE-2024-1102 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat JBoss Enterprise Application Platform 7.4.16 | org.jberet/jberet-core:1.3.9.SP3-redhat-00001 | RHSA-2024:1677 |
| Red Hat JBoss Enterprise Application Platform 8 | jberet-core | RHSA-2024:3583 |
| Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 8 | eap8-hibernate-search-0:6.2.2-1.Final_redhat_00001.1.el8eap | RHSA-2024:3580 |
| Red Hat JBoss Enterprise Application Platform 8.0 for RHEL 9 | eap8-hibernate-search-0:6.2.2-1.Final_redhat_00001.1.el9eap | RHSA-2024:3581 |
Frequently Asked Questions
Is CVE-2024-1102 in your dependencies?
Find it across Maven, including transitive dependencies.