CVE-2023-32187

Mitigation

If you cannot upgrade to a fixed release, the certificate can be "frozen" by running the following command against the cluster:

kubectl annotate secret -n kube-system k3s-serving listener.cattle.io/static=true

⚠️ IMPORTANT CAUTION: Note that this mitigation will prevent the certificate from adding new SAN entries when servers join the cluster, and automatically renewing itself when it is about to expire. If you do this, you should delete the annotation when adding new servers to the cluster, or when the certificate is within 90 days of expiring, so that it can be updated. Once that is done, you can freeze it again.

Affected certificates can be reset by performing the following steps:

1. Run kubectl --server https://localhost:6444 delete secret -n kube-system k3s-serving
2. Delete /var/lib/rancher/k3s/server/tls/dynamic-cert.json from all servers, and restart the k3s service.

Background

The K3s apiserver/supervisor listener on port TCP 6443 and uses the rancher/dynamiclistener library to dynamically generate TLS certificates that contain TLS Subject Alternative Names (SAN) for any host name or IP address requested by a client. This is done to allow servers and external load-balancers to be added to the cluster without the administrator having to explicitly know and configure in advance a fixed list of endpoints that the supervisor may be hosted at.

The library allows the embedding application to configure a callback that is used to filter addresses requested by clients; but this was not previously implemented in K3s.

For more information

If you have any questions or comments about this advisory:

• Reach out to the K3s Security team for security related inquiries.
• Open an issue in the K3s repository.
• Verify with our support matrix and product support lifecycle.

An issue was found in K3s where an attacker with network access to K3s servers' apiserver/supervisor port (TCP 6443) can force the TLS server to add entries to the certificate's Subject Alternative Name (SAN) list, through a stuffing attack, until the certificate grows so large that it exceeds the maximum size allowed by TLS client implementations. OpenSSL for example will raise an excessive message size error when this occurs. No authentication is necessary to perform this attack, only the ability to perform a TLS handshake against the apiserver/supervisor port (TCP 6443).

Affected servers will continue to operate, but clients (including both external administrative access with kubectl and server or agent nodes) will fail to establish new connections, thus leading to a denial of service (DoS) attack.

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

CVE-2023-32187 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.24.17, 1.25.13, 1.26.8, 1.27.5, 1.28.1); upgrading removes the vulnerable code path.

Kodem intelligence

Upgrade to a fixed release:

• v1.28.1+k3s1
• v1.27.5+k3s1
• v1.26.8+k3s1
• v1.25.13+k3s1
• v1.24.17+k3s1

If you are using K3s 1.27 or earlier, you must also add the parameter tls-san-security: true to the K3s configuration to enable enhanced security for the supervisor's TLS SAN list. This option defaults to true starting with K3s 1.28.

Note that this flag changes the behavior of K3s servers. You should ensure that you configure node-external-ip on servers that will be connected to via an external IP, and add tls-san entries for any load-balancers or VIP addresses that will be associated with the supervisor port. External IPs and load-balancer/VIP addresses will no longer be added to the supervisor certificate's SAN list unless explicitly configured.

1. What is CVE-2023-32187? CVE-2023-32187 is a high-severity allocation of resources without limits or throttling vulnerability in github.com/k3s-io/k3s (go), affecting versions < 1.24.17. It is fixed in 1.24.17, 1.25.13, 1.26.8, 1.27.5, 1.28.1. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.
2. How severe is CVE-2023-32187? CVE-2023-32187 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/k3s-io/k3s are affected by CVE-2023-32187? github.com/k3s-io/k3s (go) versions < 1.24.17 is affected.
4. Is there a fix for CVE-2023-32187? Yes. CVE-2023-32187 is fixed in 1.24.17, 1.25.13, 1.26.8, 1.27.5, 1.28.1. Upgrade to this version or later.
5. Is CVE-2023-32187 exploitable, and should I be worried? Whether CVE-2023-32187 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-32187 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-32187?
   • Upgrade github.com/k3s-io/k3s to 1.24.17 or later
   • Upgrade github.com/k3s-io/k3s to 1.25.13 or later
   • Upgrade github.com/k3s-io/k3s to 1.26.8 or later
   • Upgrade github.com/k3s-io/k3s to 1.27.5 or later
   • Upgrade github.com/k3s-io/k3s to 1.28.1 or later