Credential disclosure via unredacted debug logging
Published Mar 28, 2025 · Updated Mar 20, 2026
Information disclosure in ansible-rulebook before 1.1.6 allows remote authenticated users to read inventory and PostgreSQL passwords from logs. Event-Driven Ansible debug actions write inventory values to activation logs without redacting passwords, while Event Streams also emit PostgreSQL passwords. A low-privilege platform account and a debug-configured activation are required, and exposure is limited to credentials present in the emitted log data.
Summary
What happened
Information disclosure in ansible-rulebook before 1.1.6 allows remote authenticated users to read inventory and PostgreSQL passwords from logs. Event-Driven Ansible debug actions write inventory values to activation logs without redacting passwords, while Event Streams also emit PostgreSQL passwords. A low-privilege platform account and a debug-configured activation are required, and exposure is limited to credentials present in the emitted log data.
The record
- CVE
- CVE-2025-2877
- Published
- Mar 28, 2025
- Updated
- Mar 20, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat Ansible Automation Platform
- Classifications
- CWE-1295, T1552.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 28, 2025CVE publishedPublication date reported by the CVE source.
- Mar 20, 2026Record 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.
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