Security readout for executives and security teams
Plain-English summary
Redpanda rpk import could print AWS access keys and secrets to console output before the fixed releases. If logs are collected, those credentials may also land in Kubernetes logs. This is not a remote code execution issue, but leaked cloud credentials can create serious downstream business risk.
Executive priority
Treat this as a focused credential hygiene issue. Prioritize teams using Redpanda import with AWS credentials, especially in Kubernetes or centralized logging environments. The business urgency comes from possible cloud credential exposure rather than broad remote exploitability.
Technical view
CVE-2023-24619 is a CWE-522 cleartext credential disclosure in Redpanda rpk import before 22.3.12. The AWS Access Key ID and Secret were logged to standard output. Exposure requires local visibility into the console output or access to collected stdout logs, including Kubernetes log aggregation.
Likely exposure
Organizations using Redpanda rpk import with AWS credentials before versions 22.3.12, 22.2.10, or 22.1.12 are the likely exposure group. Risk is higher where stdout is centrally collected, retained, or accessible to operators beyond the importing user.
Exploitation context
The source bundle does not cite active exploitation, and the CVE is not marked KEV. Abuse depends on access to local console output or collected logs containing the printed credentials. The main impact is confidentiality loss of AWS credentials, not direct service compromise.
Researcher notes
The CVSS vector is local, low complexity, low privilege, no user interaction, unchanged scope, high confidentiality impact. Public evidence in the bundle names fixed versions and the cleartext stdout behavior, but does not provide broader exploit telemetry or affected CPE detail.
Mitigation direction
- Upgrade Redpanda to 22.3.12, 22.2.10, 22.1.12, or later supported versions.
- Rotate any AWS credentials used with affected rpk import workflows.
- Review Kubernetes and centralized logs for accidental credential retention.
- Restrict access to historical logs that may contain sensitive output.
- Check Redpanda vendor guidance for any additional remediation instructions.
Validation and detection
- Inventory Redpanda and rpk versions used by operators and automation.
- Identify rpk import workflows that used AWS credentials before fixed versions.
- Check whether stdout from import jobs was collected into Kubernetes or central logs.
- Confirm exposed AWS keys were rotated and old keys disabled.
- Verify upgraded rpk no longer logs AWS credentials in cleartext.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-522: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2023-24619 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N1.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/redpanda-data/redpanda/pull/8339CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insufficiently Protected Credentials
Insufficiently Protected Credentials represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.