Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

k3s · denial of service

CVSS 3.1 7.5 HIGHEUVD CVSS 3.1 7.5 CVSS 3.1 · [email protected] · Secondary 7.5 HIGHCVSS 3.1 · [email protected] · Primary 7.5 HIGHCVSS_V3 Publisher rating HIGHFixed by github.com/k3s-io/k3s 1.24.17Fixed by github.com/k3s-io/k3s 1.25.13Fixed by github.com/k3s-io/k3s 1.26.8Fixed by github.com/k3s-io/k3s 1.27.5KEV status unknown

cve-program · CVE-2023-32187

Published

An Allocation of Resources Without Limits or Throttling vulnerability in SUSE k3s allows attackers with access to K3s servers' apiserver/supervisor port (TCP 6443) cause denial of service. This issue affects k3s: from v1.24.0 before v1.24.17+k3s1, from v1.25.0 before v1.25.13+k3s1, from v1.26.0 before v1.26.8+k3s1, from sev1.27.0 before v1.27.5+k3s1, from v1.28.0 before v1.28.1+k3s1.

Read the publisher's advisory

euvd · EUVD-2023-2541

Published

An Allocation of Resources Without Limits or Throttling vulnerability in SUSE k3s allows attackers with access to K3s servers' apiserver/supervisor port (TCP 6443) cause denial of service. This issue affects k3s: from v1.24.0 before v1.24.17+k3s1, from v1.25.0 before v1.25.13+k3s1, from v1.26.0 before v1.26.8+k3s1, from sev1.27.0 before v1.27.5+k3s1, from v1.28.0 before v1.28.1+k3s1.

Read the publisher's advisory

nvd · CVE-2023-32187

Published

An Allocation of Resources Without Limits or Throttling vulnerability in SUSE k3s allows attackers with access to K3s servers' apiserver/supervisor port (TCP 6443) cause denial of service. This issue affects k3s: from v1.24.0 before v1.24.17+k3s1, from v1.25.0 before v1.25.13+k3s1, from v1.26.0 before v1.26.8+k3s1, from sev1.27.0 before v1.27.5+k3s1, from v1.28.0 before v1.28.1+k3s1.

Read the publisher's advisory

osv · GHSA-m4hf-6vgr-75r2

Published

### Impact 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. ### Remediation 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. ### Mitigation If you cannot upgrade to a fixed release, the certificate can be "frozen" by running the following command against the cluster: ```shell 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](https://github.com/k3s-io/k3s/security/policy) for security related inquiries. - Open an issue in the [K3s](https://github.com/k3s-io/k3s/issues/new/choose) repository. - Verify with our [support matrix](https://www.suse.com/suse-k3s/support-matrix/all-supported-versions) and [product support lifecycle](https://www.suse.com/lifecycle/#k3s).

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2023-32187

Published

k3s

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "defaultStatus": "unaffected",
                    "packageName": "k3s",
                    "product": "k3s",
                    "vendor": "SUSE",
                    "versions": [
                        {
                            "lessThan": "v1.24.17+k3s1",
                            "status": "affected",
                            "version": "v1.24.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThan": "v1.25.13+k3s1",
                            "status": "affected",
                            "version": "v1.25.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThan": "v1.26.8+k3s1",
                            "status": "affected",
                            "version": "v1.26.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThan": "v1.27.5+k3s1",
                            "status": "affected",
                            "version": "sev1.27.0",
                            "versionType": "semver"
                        },
                        {
                            "lessThan": "v1.28.1+k3s1",
                            "status": "affected",
                            "version": "v1.28.0",
                            "versionType": "semver"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2023-2541

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Sep 18, 2023, 12:04:27 PM

dateUpdated: Sep 25, 2024, 8:48:50 PM

1 related source bulletins · separate from aliases

WID-SEC-W-2023-2303: Kubernetes: Schwachstelle ermöglicht Denial of Service

CVE-2023-32187

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2023-32187

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-770

Original publisher date fields

published: 2023-09-18T13:15:08.190

lastModified: 2026-06-17T05:58:16.547

1 source CPE criteria · context only
  • cpe:2.3:a:k3s:k3s:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-m4hf-6vgr-75r2

Published

github.com/k3s-io/k3s

Go

SEMVER · introduced 0 → fixed 1.24.17

github.com/k3s-io/k3s

Go

SEMVER · introduced 1.25.0 → fixed 1.25.13

github.com/k3s-io/k3s

Go

SEMVER · introduced 1.26.0 → fixed 1.26.8

github.com/k3s-io/k3s

Go

SEMVER · introduced 1.27.0 → fixed 1.27.5

github.com/k3s-io/k3s

Go

SEMVER · introduced 1.28.0 → fixed 1.28.1

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 04:49 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current