AWS credential disclosure via unredacted import output
Published Feb 13, 2023 · Updated Mar 21, 2025
Credential disclosure in Redpanda rpk before 22.3.12 allows local users to read AWS access keys and secrets from command output. The cluster config import and edit paths print raw cloud_storage_secret_key and cloud_storage_azure_shared_key values instead of replacing secrets with a redaction marker. Access to the invoking console or collected Kubernetes stdout is required, and exposure is limited to credential confidentiality.
Summary
What happened
Credential disclosure in Redpanda rpk before 22.3.12 allows local users to read AWS access keys and secrets from command output. The cluster config import and edit paths print raw cloud_storage_secret_key and cloud_storage_azure_shared_key values instead of replacing secrets with a redaction marker. Access to the invoking console or collected Kubernetes stdout is required, and exposure is limited to credential confidentiality.
The record
- CVE
- CVE-2023-24619
- Published
- Feb 13, 2023
- Updated
- Mar 21, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-522, T1552
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 13, 2023CVE publishedPublication date reported by the CVE source.
- Mar 21, 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?
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.
Public exploit references
- rpk cluster configuration import disclosure demonstrationproof of concept · demonstrated
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