# Jberet: jberet-core logging database credentials

Advisory record · `GHSA-9wmf-xf3h-r8pr`

- **Identifiers:** `GHSA-9wmf-xf3h-r8pr` · `CVE-2024-1102`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-523](https://cwe.mitre.org/data/definitions/523.html) · [CWE-532](https://cwe.mitre.org/data/definitions/532.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [CWE-523](https://agentprime.io/advisories/tag/cwe-523.md)
- **Published:** 25 Apr 2024
- **Updated:** 24 Oct 2025
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 25 Apr 2024, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `org.jberet:jberet-core` (Maven): affected `<2.2.1.Final`; fixed in `2.2.1.Final`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`, from CNA (redhat)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0081, the 56th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:10 UTC: First seen by agentprime
- 31 Oct 2026, 15:10 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-9wmf-xf3h-r8pr)

## Sources

- [GitHub Advisory Database: GHSA-9wmf-xf3h-r8pr](https://github.com/advisories/GHSA-9wmf-xf3h-r8pr)
- [OSV: GHSA-9wmf-xf3h-r8pr](https://osv.dev/vulnerability/GHSA-9wmf-xf3h-r8pr)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-1102>
- <https://github.com/jberet/jsr352/issues/452>
- <https://github.com/jberet/jsr352/commit/eeef999663d7da0e372aeeeac26ecf7201a3121d>
- <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>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-9wmf-xf3h-r8pr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-9wmf-xf3h-r8pr/>. Everything for agents: <https://agentprime.io/llms.txt>.