Jberet: jberet-core logging database credentials
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.2.1, 2.2.1.Final
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- 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-coreMaven
fixed in 2.2.1.Final