REDHAT-BUG-1936629
First published: Mon Mar 08 2021(Updated: )
A flaw was found in the AMQ Broker that discloses JDBC encrypted usernames and passwords when provided in the AMQ Broker application logfile when using the jdbc persistence functionality
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Red Hat AMQ |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of REDHAT-BUG-1936629?
The severity of REDHAT-BUG-1936629 is deemed critical due to the potential exposure of sensitive JDBC encrypted usernames and passwords.
How do I fix REDHAT-BUG-1936629?
To fix REDHAT-BUG-1936629, it is recommended to upgrade to the patched version of Red Hat AMQ Broker provided in the latest security advisories.
What does REDHAT-BUG-1936629 affect?
REDHAT-BUG-1936629 affects the Red Hat AMQ Broker, specifically the JDBC persistence functionality.
What information is disclosed in REDHAT-BUG-1936629?
REDHAT-BUG-1936629 discloses JDBC encrypted usernames and passwords through the AMQ Broker application's logfile.
Is there a workaround for REDHAT-BUG-1936629?
Currently, there is no specific workaround for REDHAT-BUG-1936629 provided, and updating to a secure version is the best course of action.
- agent/references
- agent/type
- agent/first-publish-date
- agent/last-modified-date
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2021-3425
- agent/source
- agent/description
- agent/severity
- agent/event
- agent/tags
- agent/softwarecombine
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- vendor/red hat
- canonical/red hat amq