CVE-2021-3425
CVE-2021-3425 is a medium-severity vulnerability in Redhat Jboss A-mq with a CVSS 3.x base score of 4.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-532.
Key facts
- Severity: Medium (CVSS 3.x base score 4.4)
- CVSS v2: 2.1
- EPSS exploit prediction: 0% (20th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-532
- Affected product: Redhat Jboss A-mq
- Published:
- Last modified:
Description
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. Versions shipped in Red Hat AMQ 7 are vulnerable.
Frequently asked questions
- What is CVE-2021-3425?
- 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. Versions shipped in Red Hat AMQ 7 are vulnerable.
- How severe is CVE-2021-3425?
- CVE-2021-3425 has a CVSS 3.x base score of 4.4, rated medium severity. It is exploitable over local access with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
- Is CVE-2021-3425 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (20th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2021-3425?
- CVE-2021-3425 affects Redhat Jboss A-mq. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2021-3425?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2021-3425 published?
- CVE-2021-3425 was published on 2021-06-01 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:redhat:jboss_a-mq:7:*:*:*:*:*:*:*
More vulnerabilities in Redhat Jboss A-mq
- CVE-2015-7501 — Critical (CVSS 9.8): Red Hat JBoss A-MQ 6.x; BPM Suite (BPMS) 6.x; BRMS 6.x and 5.x; Data Grid (JDG) 6.x; Data Virtualization (JDV) 6.x and…
- CVE-2023-44487 — High (CVSS 7.5): The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset…
- CVE-2022-1278 — High (CVSS 7.5): A flaw was found in WildFly, where an attacker can see deployment names, endpoints, and any other data the trace…
- CVE-2021-4104 — High (CVSS 7.5): JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the…
- CVE-2015-5183 — High (CVSS 7.5): Console: HTTPOnly and Secure attributes not set on cookies in Red Hat AMQ.
- CVE-2016-8648 — High (CVSS 7.2): It was found that the Karaf container used by Red Hat JBoss Fuse 6.x, and Red Hat JBoss A-MQ 6.x, deserializes objects…
All CVEs affecting Redhat Jboss A-mq →
Other CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities
- CVE-2022-36407 — Critical (CVSS 9.9): Insertion of Sensitive Information into Log File vulnerability in Hitachi Virtual Storage Platform, Hitachi Virtual…
- CVE-2023-40029 — Critical (CVSS 9.9): Argo CD is a declarative continuous deployment for Kubernetes. Argo CD Cluster secrets might be managed declaratively…
- CVE-2021-32724 — Critical (CVSS 9.9): check-spelling is a github action which provides CI spell checking. In affected versions and for a repository with the…
- CVE-2026-49200 — Critical (CVSS 9.8): The acer_cgi.log file in the device firmware is accessible without authentication via the web interface. This file…
- CVE-2026-22778 — Critical (CVSS 9.8): vLLM is an inference and serving engine for large language models (LLMs). From 0.8.3 to before 0.14.1, when an invalid…
- CVE-2025-11008 — Critical (CVSS 9.8): The CE21 Suite plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and…
Browse all CWE-532 (Insertion of Sensitive Information into Log File) vulnerabilities →