Security readout for executives and security teams
Plain-English summary
In affected K3s and RKE2 clusters, sensitive bootstrap material may be protected with an empty password when no token was supplied. Anyone who can access the datastore or a datastore backup could decrypt cluster CA private keys and other secrets without knowing the token.
Executive priority
Prioritize this as a confidentiality risk for affected Rancher-managed Kubernetes environments. It is not described as remotely exploitable by outsiders, but compromise of backups or datastore access could expose high-value cluster trust material.
Technical view
CVE-2021-32001 is a CWE-311 exposure in SUSE Rancher K3s and RKE2. Affected versions include v1.19.12, v1.20.8, v1.21.2 release lines and prior. The issue impacts confidentiality only: bootstrap data can be decrypted from datastore contents or backups when token handling falls back to an empty string.
Likely exposure
Exposure is most likely in affected K3s or RKE2 deployments where operators did not supply a token and where datastore access or backup access is available to users, administrators, service accounts, or backup systems.
Exploitation context
The sources do not report active exploitation, and CISA KEV status is false. Abuse requires access to the datastore or a datastore backup, but the disclosed impact is serious because cluster key material and encryption passphrases may be exposed.
Researcher notes
The public bundle gives impact and affected ranges but does not provide detailed patch identifiers or exploit evidence. Focus validation on version, bootstrap token configuration, datastore access paths, and backup custody rather than assuming internet-wide exploitability.
Mitigation direction
- Identify all K3s and RKE2 clusters and record exact versions.
- Check SUSE/Rancher guidance for fixed releases and upgrade to a non-affected version.
- Review whether a token was explicitly supplied during cluster bootstrap.
- Restrict datastore and backup access to the smallest necessary administrator set.
- Rotate exposed cluster secrets and key material if datastore backup access was untrusted.
Validation and detection
- Confirm whether deployed K3s or RKE2 versions are within the affected ranges.
- Review cluster creation records for missing user-supplied token configuration.
- Audit datastore and backup access logs for unexpected access.
- Inventory backup locations and verify encryption, retention, and access controls.
- Treat accessible historical backups as potentially sensitive until assessed.
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-311: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCVE-2021-32001 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
- 6.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/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:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://bugzilla.suse.com/show_bug.cgi?id=1188453CVE 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.
Missing Encryption of Sensitive Data
Missing Encryption of Sensitive Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.