Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom resources of a different type in the same API group without authorization. Clusters are impacted by this vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The same users are not authorized to read another custom resource in the same API group.

The remote Red Hat Enterprise Linux CoreOS 4 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2022:7398 advisory.

  - Due to unbounded alias chasing, a maliciously crafted YAML file can cause the system to consume     significant system resources. If parsing user input, this may be used as a denial of service vector.
    (CVE-2021-4235)

  - Acceptance of some invalid Transfer-Encoding headers in the HTTP/1 client in net/http before Go 1.17.12     and Go 1.18.4 allows HTTP request smuggling if combined with an intermediate server that also improperly     fails to reject the header as invalid. (CVE-2022-1705)

  - In net/http in Go before 1.18.6 and 1.19.x before 1.19.1, attackers can cause a denial of service because     an HTTP/2 connection can hang during closing if shutdown were preempted by a fatal error. (CVE-2022-27664)

  - Reader.Read does not set a limit on the maximum size of file headers. A maliciously crafted archive could     cause Read to allocate unbounded amounts of memory, potentially causing resource exhaustion or panics.
    After fix, Reader.Read limits the maximum size of header blocks to 1 MiB. (CVE-2022-2879)

  - Requests forwarded by ReverseProxy include the raw query parameters from the inbound request, including     unparsable parameters rejected by net/http. This could permit query parameter smuggling when a Go proxy     forwards a parameter with an unparsable value. After fix, ReverseProxy sanitizes the query parameters in     the forwarded query when the outbound request's Form field is set after the ReverseProxy. Director     function returns, indicating that the proxy has parsed the query parameters. Proxies which do not parse     query parameters continue to forward the original query parameters unchanged. (CVE-2022-2880)

  - Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive     information disclosure or possible data modification if an attacker has direct access to the affected     container where supplementary groups are used to set access permissions and is able to execute a binary     code in that container. (CVE-2022-2995)

  - python-scciclient: missing server certificate verification (CVE-2022-2996)

  - Uncontrolled recursion in Reader.Read in compress/gzip before Go 1.17.12 and Go 1.18.4 allows an attacker     to cause a panic due to stack exhaustion via an archive containing a large number of concatenated 0-length     compressed files. (CVE-2022-30631)

  - Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom     resources of a different type in the same API group without authorization. Clusters are impacted by this     vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same     API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The     same users are not authorized to read another custom resource in the same API group. (CVE-2022-3162)

  - A security issue was discovered in kube-apiserver that allows an aggregated API server to redirect client     traffic to any URL. This could lead to the client performing unexpected actions as well as forwarding the     client's API server credentials to third parties. (CVE-2022-3172)

  - Improper exposure of client IP addresses in net/http before Go 1.17.12 and Go 1.18.4 can be triggered by     calling httputil.ReverseProxy.ServeHTTP with a Request.Header map containing a nil value for the     X-Forwarded-For header, which causes ReverseProxy to set the client IP as the value of the X-Forwarded-For     header. (CVE-2022-32148)

  - A too-short encoded message can cause a panic in Float.GobDecode and Rat GobDecode in math/big in Go     before 1.17.13 and 1.18.5, potentially allowing a denial of service. (CVE-2022-32189)

  - JoinPath and URL.JoinPath do not remove ../ path elements appended to a relative path. For example,     JoinPath(https://go.dev, ../go) returns the URL https://go.dev/../go, despite the JoinPath     documentation stating that ../ path elements are removed from the result. (CVE-2022-32190)

  - Openshift 4.9 does not use HTTP Strict Transport Security (HSTS) which may allow man-in-the-middle (MITM)     attacks. (CVE-2022-3259)

  - The version of cri-o as released for Red Hat OpenShift Container Platform 4.9.48, 4.10.31, and 4.11.6 via     RHBA-2022:6316, RHBA-2022:6257, and RHBA-2022:6658, respectively, included an incorrect version of cri-o     missing the fix for CVE-2022-27652, which was previously fixed in OCP 4.9.41 and 4.10.12 via     RHBA-2022:5433 and RHSA-2022:1600. This issue could allow an attacker with access to programs with     inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs. For     more details, see https://access.redhat.com/security/cve/CVE-2022-27652. (CVE-2022-3466)

  - Programs which compile regular expressions from untrusted sources may be vulnerable to memory exhaustion     or denial of service. The parsed regexp representation is linear in the size of the input, but in some     cases the constant factor can be as high as 40,000, making relatively small regexps consume much larger     amounts of memory. After fix, each regexp being parsed is limited to a 256 MB memory footprint. Regular     expressions whose representation would use more space than that are rejected. Normal use of regular     expressions is unaffected. (CVE-2022-41715)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Red Hat Enterprise Linux CoreOS 4 host has packages installed that are affected by a vulnerability as referenced in the RHSA-2023:0772 advisory.

  - Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom     resources of a different type in the same API group without authorization. Clusters are impacted by this     vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same     API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The     same users are not authorized to read another custom resource in the same API group. (CVE-2022-3162)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2023:2292-1 advisory.

  - Windows workloads can run as ContainerAdministrator even when those workloads set the runAsNonRoot option     to true. (CVE-2021-25749)

  - Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom     resources of a different type in the same API group without authorization. Clusters are impacted by this     vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same     API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The     same users are not authorized to read another custom resource in the same API group. (CVE-2022-3162)

  - Users may have access to secure endpoints in the control plane network. Kubernetes clusters are only     affected if an untrusted user can modify Node objects and send proxy requests to them. Kubernetes supports     node proxying, which allows clients of kube-apiserver to access endpoints of a Kubelet to establish     connections to Pods, retrieve container logs, and more. While Kubernetes already validates the proxying     address for Nodes, a bug in kube-apiserver made it possible to bypass this validation. Bypassing this     validation could allow authenticated requests destined for Nodes to to the API server's private network.
    (CVE-2022-3294)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Fedora 35 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2022-2004702d98 advisory.

  - Resolves, in part, #2142161. Security patches that resolve CVE-2022-3162 and CVE-2022-3294.
    (CVE-2022-3162, CVE-2022-3294)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Oracle Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2022-10036 advisory.

  - Users may have access to secure endpoints in the control plane network. Kubernetes clusters are only     affected if an untrusted user can modify Node objects and send proxy requests to them. Kubernetes supports     node proxying, which allows clients of kube-apiserver to access endpoints of a Kubelet to establish     connections to Pods, retrieve container logs, and more. While Kubernetes already validates the proxying     address for Nodes, a bug in kube-apiserver made it possible to bypass this validation. Bypassing this     validation could allow authenticated requests destined for Nodes to to the API server's private network.
    (CVE-2022-3294)

  - Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom     resources of a different type in the same API group without authorization. Clusters are impacted by this     vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same     API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The     same users are not authorized to read another custom resource in the same API group. (CVE-2022-3162)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Oracle Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2022-10035 advisory.

  - Users may have access to secure endpoints in the control plane network. Kubernetes clusters are only     affected if an untrusted user can modify Node objects and send proxy requests to them. Kubernetes supports     node proxying, which allows clients of kube-apiserver to access endpoints of a Kubelet to establish     connections to Pods, retrieve container logs, and more. While Kubernetes already validates the proxying     address for Nodes, a bug in kube-apiserver made it possible to bypass this validation. Bypassing this     validation could allow authenticated requests destined for Nodes to to the API server's private network.
    (CVE-2022-3294)

  - Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom     resources of a different type in the same API group without authorization. Clusters are impacted by this     vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same     API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The     same users are not authorized to read another custom resource in the same API group. (CVE-2022-3162)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Oracle Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2022-10034 advisory.

  - Users may have access to secure endpoints in the control plane network. Kubernetes clusters are only     affected if an untrusted user can modify Node objects and send proxy requests to them. Kubernetes supports     node proxying, which allows clients of kube-apiserver to access endpoints of a Kubelet to establish     connections to Pods, retrieve container logs, and more. While Kubernetes already validates the proxying     address for Nodes, a bug in kube-apiserver made it possible to bypass this validation. Bypassing this     validation could allow authenticated requests destined for Nodes to to the API server's private network.
    (CVE-2022-3294)

  - Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom     resources of a different type in the same API group without authorization. Clusters are impacted by this     vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same     API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The     same users are not authorized to read another custom resource in the same API group. (CVE-2022-3162)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote Oracle Linux 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2022-10033 advisory.

  - Users may have access to secure endpoints in the control plane network. Kubernetes clusters are only     affected if an untrusted user can modify Node objects and send proxy requests to them. Kubernetes supports     node proxying, which allows clients of kube-apiserver to access endpoints of a Kubelet to establish     connections to Pods, retrieve container logs, and more. While Kubernetes already validates the proxying     address for Nodes, a bug in kube-apiserver made it possible to bypass this validation. Bypassing this     validation could allow authenticated requests destined for Nodes to to the API server's private network.
    (CVE-2022-3294)

  - Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom     resources of a different type in the same API group without authorization. Clusters are impacted by this     vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same     API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The     same users are not authorized to read another custom resource in the same API group. (CVE-2022-3162)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
189448	RHCOS 4 : OpenShift Container Platform 4.12.0 (RHSA-2022:7398)	Nessus	Red Hat Local Security Checks	high
189421	RHCOS 4 : OpenShift Container Platform 4.12.4 (RHSA-2023:0772)	Nessus	Red Hat Local Security Checks	medium
176412	SUSE SLES15 Security Update : kubernetes1.23 (SUSE-SU-2023:2292-1)	Nessus	SuSE Local Security Checks	high
169038	Fedora 35 : kubernetes (2022-2004702d98)	Nessus	Fedora Local Security Checks	high
168283	Oracle Linux 8 : kubernetes (ELSA-2022-10036)	Nessus	Oracle Linux Local Security Checks	high
168278	Oracle Linux 7 : kubernetes (ELSA-2022-10035)	Nessus	Oracle Linux Local Security Checks	high
168277	Oracle Linux 8 : kubernetes (ELSA-2022-10034)	Nessus	Oracle Linux Local Security Checks	high
168276	Oracle Linux 7 : kubernetes (ELSA-2022-10033)	Nessus	Oracle Linux Local Security Checks	high

Detections

Analytics

CVE-2022-3162

medium

Tenable Plugins

high

medium

high

high

high

high

high

high