Credential disclosure via generated repository filenames
Published Feb 20, 2020 · Updated Aug 6, 2024
Information disclosure in Ansible before 1.5.5 allows local users to obtain repository credentials from generated filenames. The apt_repository module's SourcesList._suggest_filename method converts an authenticated APT source URL into a .list filename without first removing its user and password fields. Exposure requires a deb entry containing embedded HTTP credentials and a local user able to observe the resulting filename; no data modification or service interruption is reported.
Summary
What happened
Information disclosure in Ansible before 1.5.5 allows local users to obtain repository credentials from generated filenames. The apt_repository module's SourcesList._suggest_filename method converts an authenticated APT source URL into a .list filename without first removing its user and password fields. Exposure requires a deb entry containing embedded HTTP credentials and a local user able to observe the resulting filename; no data modification or service interruption is reported.
The record
- CVE
- CVE-2014-4660
- Published
- Feb 20, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-522, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 20, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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