Skip to content
Fencer Intel
critical 9.9

CVE-2023-32191 json

rke's credentials are stored in the RKE1 Cluster state ConfigMap

published 2y ago modified 4mo ago also GHSA-6gr4-52w6-vmqx , GO-2024-2930 , EUVD-2024-1950

cvss
9.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

When RKE provisions a cluster, it stores the cluster state in a configmap called `full-cluster-state` inside the `kube-system` namespace of the cluster itself. The information available in there allows non-admin users to escalate to admin.

Patch / fix

  • go github.com/rancher/rke 1.4.19, 1.5.10
  • SUSE rke 1.4.19, 1.5.10

Is CVE-2023-32191 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

0.66% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 9.9 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/rancher/rke
>=1.4.18, <1.4.19
>=1.5.9, <1.5.10
1.4.19
1.5.10

Affected products

  • SUSE rke

Classification

Weakness
  • CWE-922 Insecure Storage of Sensitive Information

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.