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

> An exception in jberet-core logging may expose database credentials, allowing attackers to read sensitive connection information.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Apr 2024
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-9wmf-xf3h-r8pr

## What is CVE-2024-1102?

CVE-2024-1102 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 25 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-523 (Unprotected Transport of Credentials)

## Which versions are affected by CVE-2024-1102?

2 open source packages ship an affected version, including org.jberet:jberet-core. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jberet:jberet-core` | Maven | All versions | 2.2.1.Final |
| `org.jberet:jberet-core` | Maven | All versions | 2.2.1.Final |

Products: Jberet Jberet, Redhat Jboss Enterprise Application Platform.

## How do I fix CVE-2024-1102?

Upgrade org.jberet:jberet-core to 2.2.1.Final or later.

## Is CVE-2024-1102 being exploited?

There is no known exploitation of CVE-2024-1102 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1102 and fix it if it is affected.

What it is: CVE-2024-1102 is a medium-severity vulnerability in Redhat Jboss Enterprise Application Platform, published on 25 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-1102 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jberet:jberet-core (Maven): affected all versions; fixed in 2.2.1.Final
- org.jberet:jberet-core (Maven): affected all versions; fixed in 2.2.1.Final

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-1102/ (Markdown: https://insights.sbomify.com/CVE-2024-1102/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1102
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1102
- OSV: https://osv.dev/vulnerability/CVE-2024-1102

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1102/
Summaries are generated and may contain mistakes; the official description above is the record.