Cross-broker access via reused generated credentials
Published May 26, 2025 · Updated Nov 20, 2025
Weak credentials in Red Hat AMQ Broker Operator before 2.0.3 allow local users to access another broker through reused credentials. ProcessCredentials used process-wide defaults for AMQ_USER, AMQ_PASSWORD, AMQ_CLUSTER_USER, and AMQ_CLUSTER_PASSWORD instead of generating values per CR. Low-privileged access to one OpenShift CR secret is required, after which identical credentials expose data protected by a separate CR.
Summary
What happened
Weak credentials in Red Hat AMQ Broker Operator before 2.0.3 allow local users to access another broker through reused credentials. ProcessCredentials used process-wide defaults for AMQ_USER, AMQ_PASSWORD, AMQ_CLUSTER_USER, and AMQ_CLUSTER_PASSWORD instead of generating values per CR. Low-privileged access to one OpenShift CR secret is required, after which identical credentials expose data protected by a separate CR.
The record
- CVE
- CVE-2025-4057
- Published
- May 26, 2025
- Updated
- Nov 20, 2025
- Vendor
- 389 Directory Server
- Product
- RHEL-8 based Middleware Containers
- Classifications
- CWE-1391, T1078
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 26, 2025CVE publishedPublication date reported by the CVE source.
- Nov 20, 2025Record 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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