CVE-2024-1102

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.5 under NVD CVSS v3. EPSS exploit probability: 0.8%, top 47% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 6.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
6.5
EG Score
6.5(medium)
EG Risk
30(Track)
EG Risk 30/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity65% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
53%
KEV
Not listed

Published

April 25, 2024

Last Modified

August 4, 2026

Advisory Details (7)

Auto-updated Aug 4, 2026
Patch available. Sources: redhat.
generic

jberet-core logging database credentials · Issue #452 · jberet/jsr352 · GitHub

https://github.com/jberet/jsr352/issues/452
redhat Patch Available

2262060 – (CVE-2024-1102) CVE-2024-1102 jberet: jberet-core logging database credentials

https://bugzilla.redhat.com/show_bug.cgi?id=2262060
redhat Patch Available

CVE-2024-1102 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2024-1102
redhat Patch Available
https://access.redhat.com/errata/RHSA-2024:3583
redhat Patch Available

Affected: Red Hat Enterprise Linux 9. Red Hat Product Security has rated this update as having a security impact of Moderate. A Common V

https://access.redhat.com/errata/RHSA-2024:3581
redhat Patch Available

Affected: Red Hat Enterprise Linux 8. Red Hat Product Security has rated this update as having a security impact of Moderate. A Common V

https://access.redhat.com/errata/RHSA-2024:3580
redhat Patch Available
https://access.redhat.com/errata/RHSA-2024:1677

Vendor Advisories for CVE-2024-1102(4)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjberet-core2024-06-04redhat
redhateap8-jberet-0:2.1.4-1.Final_redhat_00001.1.el9eap2024-06-04redhat
redhateap8-jberet-0:2.1.4-1.Final_redhat_00001.1.el8eap2024-06-04redhat
redhatorg.jberet/jberet-core:1.3.9.SP3-redhat-000012024-04-04redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.jberet:jberet-core1.0.0.Alpha1 ... 2.2.0.Final (80 versions)2.2.1.Final—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 151 total refreshes for this CVE.

  1. 2026-08-25 13:47 UTCEPSS rescore
  2. 2026-08-23 00:17 UTCEPSS rescore
  3. 2026-08-21 23:47 UTCEPSS rescore
  4. 2026-08-20 22:53 UTCEPSS rescore
  5. 2026-08-20 03:15 UTCOSV refresh
  6. 2026-08-19 17:02 UTCEPSS rescore
  7. 2026-08-18 13:46 UTCEPSS rescore
  8. 2026-08-17 13:45 UTCEPSS rescore
  9. 2026-08-16 14:54 UTCEPSS rescore
  10. 2026-08-16 02:12 UTCEPSS rescore
  11. 2026-08-15 01:28 UTCEPSS rescore
  12. 2026-08-13 21:58 UTCEPSS rescore
  13. 2026-08-12 13:49 UTCEPSS rescore
  14. 2026-08-11 13:40 UTCEPSS rescore
  15. 2026-08-10 23:58 UTCEPSS rescore
  16. 2026-08-09 13:45 UTCEPSS rescore
  17. 2026-08-09 13:45 UTCEPSS rescore
  18. 2026-08-08 16:35 UTCEPSS rescore
  19. 2026-08-07 16:25 UTCEPSS rescore
  20. 2026-08-06 13:45 UTCEPSS rescore
  21. 2026-08-05 19:15 UTCEPSS rescore
  22. 2026-08-04 22:37 UTCVendor advisory
  23. 2026-08-04 19:31 UTCEG score recompute
  24. 2026-08-04 19:31 UTCVendor advisory
  25. 2026-08-04 15:08 UTCEPSS rescore
Show 75 more
  1. 2026-08-04 10:36 UTCEPSS rescore
  2. 2026-08-04 09:52 UTCVendor advisory
  3. 2026-08-04 06:37 UTCVendor advisory
  4. 2026-08-04 05:38 UTCEG score recompute
  5. 2026-08-04 05:38 UTCVendor advisory
  6. 2026-08-03 10:34 UTCEPSS rescore
  7. 2026-08-02 02:25 UTCEPSS rescore
  8. 2026-08-02 02:25 UTCEPSS rescore
  9. 2026-08-01 06:06 UTCOSV refresh
  10. 2026-08-01 04:14 UTCEPSS rescore
  11. 2026-08-01 04:14 UTCEPSS rescore
  12. 2026-07-30 16:26 UTCEPSS rescore
  13. 2026-07-30 01:29 UTCEPSS rescore
  14. 2026-07-28 15:34 UTCEPSS rescore
  15. 2026-07-27 14:11 UTCEPSS rescore
  16. 2026-07-26 14:53 UTCEPSS rescore
  17. 2026-07-26 14:53 UTCEPSS rescore
  18. 2026-07-25 14:16 UTCEPSS rescore
  19. 2026-07-24 14:16 UTCEPSS rescore
  20. 2026-07-23 14:17 UTCEPSS rescore
  21. 2026-07-23 14:17 UTCEPSS rescore
  22. 2026-07-23 02:31 UTCEG score recompute
  23. 2026-07-22 23:18 UTCEG score recompute
  24. 2026-07-22 14:07 UTCEPSS rescore
  25. 2026-07-21 15:23 UTCEPSS rescore
  26. 2026-07-20 17:06 UTCEPSS rescore
  27. 2026-07-19 14:30 UTCEPSS rescore
  28. 2026-07-19 14:30 UTCEPSS rescore
  29. 2026-07-19 02:27 UTCEPSS rescore
  30. 2026-07-18 10:03 UTCEPSS rescore
  31. 2026-07-18 10:03 UTCEPSS rescore
  32. 2026-07-15 16:56 UTCEPSS rescore
  33. 2026-07-15 16:56 UTCEPSS rescore
  34. 2026-07-15 01:59 UTCEPSS rescore
  35. 2026-07-15 01:59 UTCEPSS rescore
  36. 2026-07-14 13:25 UTCOSV refresh
  37. 2026-07-13 22:28 UTCEPSS rescore
  38. 2026-07-13 06:11 UTCEPSS rescore
  39. 2026-07-13 06:11 UTCEPSS rescore
  40. 2026-07-12 05:45 UTCEPSS rescore
  41. 2026-07-12 05:45 UTCEPSS rescore
  42. 2026-07-11 08:26 UTCEPSS rescore
  43. 2026-07-09 19:09 UTCEPSS rescore
  44. 2026-07-08 15:13 UTCEPSS rescore
  45. 2026-07-07 13:45 UTCEPSS rescore
  46. 2026-07-07 13:45 UTCEPSS rescore
  47. 2026-07-06 16:26 UTCEPSS rescore
  48. 2026-07-06 02:22 UTCEPSS rescore
  49. 2026-07-06 02:22 UTCEPSS rescore
  50. 2026-07-05 02:29 UTCEPSS rescore
  51. 2026-07-04 06:30 UTCEPSS rescore
  52. 2026-07-04 06:30 UTCEPSS rescore
  53. 2026-07-01 15:05 UTCEPSS rescore
  54. 2026-06-30 23:21 UTCEPSS rescore
  55. 2026-06-30 23:21 UTCEPSS rescore
  56. 2026-06-29 14:05 UTCEPSS rescore
  57. 2026-06-28 14:06 UTCEPSS rescore
  58. 2026-06-28 14:06 UTCEPSS rescore
  59. 2026-06-28 04:55 UTCEPSS rescore
  60. 2026-06-27 03:07 UTCEPSS rescore
  61. 2026-06-27 03:07 UTCEPSS rescore
  62. 2026-06-26 14:07 UTCOSV refresh
  63. 2026-06-25 13:48 UTCEPSS rescore
  64. 2026-06-24 14:04 UTCEPSS rescore
  65. 2026-06-24 14:04 UTCEPSS rescore
  66. 2026-06-23 21:32 UTCEPSS rescore
  67. 2026-06-23 21:31 UTCEPSS rescore
  68. 2026-06-22 14:24 UTCEPSS rescore
  69. 2026-06-22 14:24 UTCEPSS rescore
  70. 2026-06-21 14:55 UTCEPSS rescore
  71. 2026-06-21 14:55 UTCEPSS rescore
  72. 2026-06-21 01:58 UTCEPSS rescore
  73. 2026-06-21 01:58 UTCEPSS rescore
  74. 2026-06-19 19:24 UTCEPSS rescore
  75. 2026-06-19 19:24 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-1102?
CVE-2024-1102 is a medium vulnerability published on April 25, 2024. 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.
When was CVE-2024-1102 disclosed?
CVE-2024-1102 was first published in the National Vulnerability Database on April 25, 2024, with the most recent update on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-1102 actively exploited?
CVE-2024-1102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 46.6% of all scored CVEs.
What is the CVSS score of CVE-2024-1102?
CVE-2024-1102 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2024-1102?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-1102, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2024-1102

Explore →

Is Your Infrastructure Affected by CVE-2024-1102?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs