JDBC credential disclosure via application log writes
Published Jun 1, 2021 · Updated Aug 3, 2024
Sensitive-data exposure in Red Hat AMQ Broker as shipped in Red Hat AMQ 7 allows local users to read encrypted JDBC credentials from logs. When JDBC persistence is enabled, the broker writes encrypted database usernames and passwords into its application log instead of suppressing them. Local high-privileged access to the broker log is required, and the reported consequence is credential disclosure without data modification or service interruption.
Summary
What happened
Sensitive-data exposure in Red Hat AMQ Broker as shipped in Red Hat AMQ 7 allows local users to read encrypted JDBC credentials from logs. When JDBC persistence is enabled, the broker writes encrypted database usernames and passwords into its application log instead of suppressing them. Local high-privileged access to the broker log is required, and the reported consequence is credential disclosure without data modification or service interruption.
The record
- CVE
- CVE-2021-3425
- Published
- Jun 1, 2021
- Updated
- Aug 3, 2024
- Vendor
- 389 Directory Server
- Product
- Red Hat AMQ Broker
- Classifications
- CWE-532, T1552.001
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Jun 1, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=as shipped in Red Hat AMQ 7
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo