Credential disclosure via clear-text log storage
Published Jul 12, 2023 · Updated Aug 2, 2024
Clear-text credential logging in Cisco Duo Authentication Proxy allows remote authenticated users with log access to read credentials. The logging component writes certain credentials to log files without encryption, preserving the secrets in readable form. Exploitation requires authenticated access to the affected system's logs and exposes only credentials present there, with no reported integrity or availability impact.
Summary
What happened
Clear-text credential logging in Cisco Duo Authentication Proxy allows remote authenticated users with log access to read credentials. The logging component writes certain credentials to log files without encryption, preserving the secrets in readable form. Exploitation requires authenticated access to the affected system's logs and exposes only credentials present there, with no reported integrity or availability impact.
The record
- CVE
- CVE-2023-20207
- Published
- Jul 12, 2023
- Updated
- Aug 2, 2024
- Vendor
- ClamAV
- Product
- Cisco Duo Authentication Proxy
- Classifications
- CWE-532, CWE-312, T1552.001
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jul 12, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.10.0
- Affected versionversion=2.10.1
- Affected versionversion=2.11.0
- Affected versionversion=2.12.0
- Affected versionversion=2.12.1
- Affected versionversion=2.13.0
- Affected versionversion=2.14.0
- Affected versionversion=2.4.10
- Affected versionversion=2.4.11
- Affected versionversion=2.4.12
- Affected versionversion=2.4.13
- Affected versionversion=2.4.14
- Affected versionversion=2.4.14.1
- Affected versionversion=2.4.15
- Affected versionversion=2.4.16
- Affected versionversion=2.4.17
- Affected versionversion=2.4.18
- Affected versionversion=2.4.19
- Affected versionversion=2.4.2
- Affected versionversion=2.4.20
- Affected versionversion=2.4.21
- Affected versionversion=2.4.3
- Affected versionversion=2.4.4
- Affected versionversion=2.4.5
- Affected versionversion=2.4.6
- Affected versionversion=2.4.7
- Affected versionversion=2.4.8
- Affected versionversion=2.4.9
- Affected versionversion=2.5.4
- Affected versionversion=2.6.0
- Affected versionversion=2.7.0
- Affected versionversion=2.8.1
- Affected versionversion=2.9.0
- Affected versionversion=3.0.0
- Affected versionversion=3.1.0
- Affected versionversion=3.1.1
- Affected versionversion=3.2.0
- Affected versionversion=3.2.1
- Affected versionversion=3.2.2
- Affected versionversion=3.2.3
- Affected versionversion=3.2.4
- Affected versionversion=4.0.0
- Affected versionversion=4.0.1
- Affected versionversion=4.0.2
- Affected versionversion=5.0.0
- Affected versionversion=5.0.1
- Affected versionversion=5.0.2
- Affected versionversion=5.1.0
- Affected versionversion=5.1.1
- Affected versionversion=5.2.0
- Affected versionversion=5.2.1
- Affected versionversion=5.2.2
- Affected versionversion=5.3.0
- Affected versionversion=5.3.1
- Affected versionversion=5.4.0
- Affected versionversion=5.4.1
- Affected versionversion=5.5.0
- Affected versionversion=5.5.1
- Affected versionversion=5.6.0
- Affected versionversion=5.6.1
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