OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. Prior to version 0.46.0, the grpc Unary Server Interceptor out of the box adds labels `net.peer.sock.addr` and `net.peer.sock.port` that have unbound cardinality. It leads to the server's potential memory exhaustion when many malicious requests are sent. An attacker can easily flood the peer address and port for requests. Version 0.46.0 contains a fix for this issue. As a workaround to stop being affected, a view removing the attributes can be used. The other possibility is to disable grpc metrics instrumentation by passing `otelgrpc.WithMeterProvider` option with `noop.NewMeterProvider`.

The remote openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:3656-1 advisory.

    Update to version 3.5.12:

    Security fixes:

    - CVE-2018-16873: Fixed remote command execution in cmd/go (bsc#1118897)
    - CVE-2018-16874: Fixed directory traversal in cmd/go (bsc#1118898)
    - CVE-2018-16875: Fixed CPU denial of service in crypto/x509 (bsc#1118899)
    - CVE-2018-16886: Fixed improper authentication issue when RBAC and client-cert-auth is enabled     (bsc#1121850)
    - CVE-2020-15106: Fixed panic in decodeRecord method (bsc#1174951)
    - CVE-2020-15112: Fixed improper checks in entry index (bsc#1174951)
    - CVE-2021-28235: Fixed information discosure via debug function (bsc#1210138)
    - CVE-2022-41723: Fixed quadratic complexity in HPACK decoding in net/http (bsc#1208270, bsc#1208297)
    - CVE-2023-29406: Fixed insufficient sanitization of Host header in go net/http (bsc#1213229)
    - CVE-2023-47108: Fixed DoS vulnerability in otelgrpc (bsc#1217070)
    - CVE-2023-48795: Fixed prefix truncation breaking ssh channel integrity (aka Terrapin Attack) in     crypto/ssh (bsc#1217950, bsc#1218150)

    Other changes:

    - Added hardening to systemd service(s) (bsc#1181400)
    - Fixed static /tmp file issue (bsc#1199031)
    - Fixed systemd service not starting (bsc#1183703)

    Full changelog:

    https://github.com/etcd-io/etcd/compare/v3.3.1...v3.5.12

Tenable has extracted the preceding description block directly from the SUSE security advisory.

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

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

    - Update to containerd v1.7.21
    - CVE-2023-47108: Fixed DoS vulnerability in otelgrpc (uncontrolled resource consumption) due to unbound     cardinality metrics. (bsc#1217070)
    - CVE-2023-45142: Fixed DoS vulnerability in otelhttp. (bsc#1228553)

Tenable has extracted the preceding description block directly from the SUSE security advisory.

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

The remote SUSE Linux SLES12 / SLES_SAP12 host has a package installed that is affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:3188-1 advisory.

    - Update to containerd v1.7.21
    - CVE-2023-47108: Fixed DoS vulnerability in otelgrpc (uncontrolled resource consumption) due to unbound     cardinality metrics. (bsc#1217070)
    - CVE-2023-45142: Fixed DoS vulnerability in otelhttp. (bsc#1228553)

Tenable has extracted the preceding description block directly from the SUSE security advisory.

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

The version of docker-compose / docker-buildx / moby-containerd-cc / ig / containerd installed on the remote CBL Mariner 2.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2023-47108 advisory.

  - OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. Prior to version     0.46.0, the grpc Unary Server Interceptor out of the box adds labels `net.peer.sock.addr` and     `net.peer.sock.port` that have unbound cardinality. It leads to the server's potential memory exhaustion     when many malicious requests are sent. An attacker can easily flood the peer address and port for     requests. Version 0.46.0 contains a fix for this issue. As a workaround to stop being affected, a view     removing the attributes can be used. The other possibility is to disable grpc metrics instrumentation by     passing `otelgrpc.WithMeterProvider` option with `noop.NewMeterProvider`. (CVE-2023-47108)

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

The remote Redhat Enterprise Linux 8 / 9 host has a package installed that is affected by a vulnerability as referenced in the RHSA-2024:0288 advisory.

    Red Hat OpenShift Container Platform is Red Hat's cloud computing Kubernetes application platform solution     designed for on-premise or private cloud deployments.

    This advisory contains the RPM packages for Red Hat OpenShift Container Platform 4.13.30. See the     following advisory for the container images for this release:

    Security Fix(es):

    * opentelemetry-go-contrib: DoS vulnerability in otelgrpc due to unbound     cardinality metrics (CVE-2023-47108)

    For more details about the security issue(s), including the impact, a CVSS     score, acknowledgments, and other related information, refer to the CVE     page(s)     listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

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

The version of containerd installed on the remote host is prior to 1.7.11-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2ECS-2024-035 advisory.

  - A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive     server resource consumption. While the total number of requests is bounded by the     http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create     a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound     the number of simultaneously executing handler goroutines to the stream concurrency limit     (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client     has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows     too large, the server will terminate the connection. This issue is also fixed in golang.org/x/net/http2     for users manually configuring HTTP/2. The default stream concurrency limit is 250 streams (requests) per     HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the     Server.MaxConcurrentStreams setting and the ConfigureServer function. (CVE-2023-39325)

  - A malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response     body to read many more bytes from the network than are in the body. A malicious HTTP client can further     exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a     handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which     permit including additional metadata in a request or response body sent using the chunked encoding. The     net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large     metadata segment with each byte transferred. The chunk reader now produces an error if the ratio of real     body to encoded bytes grows too small. (CVE-2023-39326)

  - Text nodes not in the HTML namespace are incorrectly literally rendered, causing text which should be     escaped to not be. This could lead to an XSS attack. (CVE-2023-3978)

  - OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. Prior to version     0.46.0, the grpc Unary Server Interceptor out of the box adds labels `net.peer.sock.addr` and     `net.peer.sock.port` that have unbound cardinality. It leads to the server's potential memory exhaustion     when many malicious requests are sent. An attacker can easily flood the peer address and port for     requests. Version 0.46.0 contains a fix for this issue. As a workaround to stop being affected, a view     removing the attributes can be used. The other possibility is to disable grpc metrics instrumentation by     passing `otelgrpc.WithMeterProvider` option with `noop.NewMeterProvider`. (CVE-2023-47108)

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

The version of containerd installed on the remote host is prior to 1.7.11-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2DOCKER-2024-037 advisory.

  - A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive     server resource consumption. While the total number of requests is bounded by the     http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create     a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound     the number of simultaneously executing handler goroutines to the stream concurrency limit     (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client     has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows     too large, the server will terminate the connection. This issue is also fixed in golang.org/x/net/http2     for users manually configuring HTTP/2. The default stream concurrency limit is 250 streams (requests) per     HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the     Server.MaxConcurrentStreams setting and the ConfigureServer function. (CVE-2023-39325)

  - A malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response     body to read many more bytes from the network than are in the body. A malicious HTTP client can further     exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a     handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which     permit including additional metadata in a request or response body sent using the chunked encoding. The     net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large     metadata segment with each byte transferred. The chunk reader now produces an error if the ratio of real     body to encoded bytes grows too small. (CVE-2023-39326)

  - Text nodes not in the HTML namespace are incorrectly literally rendered, causing text which should be     escaped to not be. This could lead to an XSS attack. (CVE-2023-3978)

  - OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. Prior to version     0.46.0, the grpc Unary Server Interceptor out of the box adds labels `net.peer.sock.addr` and     `net.peer.sock.port` that have unbound cardinality. It leads to the server's potential memory exhaustion     when many malicious requests are sent. An attacker can easily flood the peer address and port for     requests. Version 0.46.0 contains a fix for this issue. As a workaround to stop being affected, a view     removing the attributes can be used. The other possibility is to disable grpc metrics instrumentation by     passing `otelgrpc.WithMeterProvider` option with `noop.NewMeterProvider`. (CVE-2023-47108)

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

The version of containerd installed on the remote host is prior to 1.7.11-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2NITRO-ENCLAVES-2024-037 advisory.

  - A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive     server resource consumption. While the total number of requests is bounded by the     http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create     a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound     the number of simultaneously executing handler goroutines to the stream concurrency limit     (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client     has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows     too large, the server will terminate the connection. This issue is also fixed in golang.org/x/net/http2     for users manually configuring HTTP/2. The default stream concurrency limit is 250 streams (requests) per     HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the     Server.MaxConcurrentStreams setting and the ConfigureServer function. (CVE-2023-39325)

  - A malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response     body to read many more bytes from the network than are in the body. A malicious HTTP client can further     exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a     handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which     permit including additional metadata in a request or response body sent using the chunked encoding. The     net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large     metadata segment with each byte transferred. The chunk reader now produces an error if the ratio of real     body to encoded bytes grows too small. (CVE-2023-39326)

  - Text nodes not in the HTML namespace are incorrectly literally rendered, causing text which should be     escaped to not be. This could lead to an XSS attack. (CVE-2023-3978)

  - OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. Prior to version     0.46.0, the grpc Unary Server Interceptor out of the box adds labels `net.peer.sock.addr` and     `net.peer.sock.port` that have unbound cardinality. It leads to the server's potential memory exhaustion     when many malicious requests are sent. An attacker can easily flood the peer address and port for     requests. Version 0.46.0 contains a fix for this issue. As a workaround to stop being affected, a view     removing the attributes can be used. The other possibility is to disable grpc metrics instrumentation by     passing `otelgrpc.WithMeterProvider` option with `noop.NewMeterProvider`. (CVE-2023-47108)

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

The remote Redhat Enterprise Linux 8 host has a package installed that is affected by a vulnerability as referenced in the RHSA-2024:0489 advisory.

    Red Hat OpenShift Container Platform is Red Hat's cloud computing Kubernetes application platform solution     designed for on-premise or private cloud deployments.

    This advisory contains the RPM packages for Red Hat OpenShift Container Platform 4.12.48. See the     following advisory for the container images for this release:

    https://access.redhat.com/errata/RHSA-2024:0485

    Security Fix(es):

    * opentelemetry-go-contrib: DoS vulnerability in otelgrpc due to unbound     cardinality metrics (CVE-2023-47108)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    All OpenShift Container Platform 4.12 users are advised to upgrade to these updated packages and images     when they are available in the appropriate release channel. To check for available updates, use the     OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at     https://docs.openshift.com/container-platform/4.12/updating/updating-cluster-cli.html

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

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

The remote Red Hat Enterprise Linux CoreOS 4 host has a package installed that is affected by a vulnerability as referenced in the RHSA-2024:0489 advisory.

  - OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. Prior to version     0.46.0, the grpc Unary Server Interceptor out of the box adds labels `net.peer.sock.addr` and     `net.peer.sock.port` that have unbound cardinality. It leads to the server's potential memory exhaustion     when many malicious requests are sent. An attacker can easily flood the peer address and port for     requests. Version 0.46.0 contains a fix for this issue. As a workaround to stop being affected, a view     removing the attributes can be used. The other possibility is to disable grpc metrics instrumentation by     passing `otelgrpc.WithMeterProvider` option with `noop.NewMeterProvider`. (CVE-2023-47108)

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

The remote Red Hat Enterprise Linux CoreOS 4 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2024:0207 advisory.

  - OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. Prior to version     0.46.0, the grpc Unary Server Interceptor out of the box adds labels `net.peer.sock.addr` and     `net.peer.sock.port` that have unbound cardinality. It leads to the server's potential memory exhaustion     when many malicious requests are sent. An attacker can easily flood the peer address and port for     requests. Version 0.46.0 contains a fix for this issue. As a workaround to stop being affected, a view     removing the attributes can be used. The other possibility is to disable grpc metrics instrumentation by     passing `otelgrpc.WithMeterProvider` option with `noop.NewMeterProvider`. (CVE-2023-47108)

  - A flaw was found in CRI-O that involves an experimental annotation leading to a container being     unconfined. This may allow a pod to specify and get any amount of memory/cpu, circumventing the kubernetes     scheduler and potentially resulting in a denial of service in the node. (CVE-2023-6476)

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

It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2024-498 advisory.

  - A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive     server resource consumption. While the total number of requests is bounded by the     http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create     a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound     the number of simultaneously executing handler goroutines to the stream concurrency limit     (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client     has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows     too large, the server will terminate the connection. This issue is also fixed in golang.org/x/net/http2     for users manually configuring HTTP/2. The default stream concurrency limit is 250 streams (requests) per     HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the     Server.MaxConcurrentStreams setting and the ConfigureServer function. (CVE-2023-39325)

  - A malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response     body to read many more bytes from the network than are in the body. A malicious HTTP client can further     exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a     handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which     permit including additional metadata in a request or response body sent using the chunked encoding. The     net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large     metadata segment with each byte transferred. The chunk reader now produces an error if the ratio of real     body to encoded bytes grows too small. (CVE-2023-39326)

  - OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. A handler wrapper     out of the box adds labels `http.user_agent` and `http.method` that have unbound cardinality. It leads to     the server's potential memory exhaustion when many malicious requests are sent to it. HTTP header User-     Agent or HTTP method for requests can be easily set by an attacker to be random and long. The library     internally uses `httpconv.ServerRequest` that records every value for HTTP `method` and `User-Agent`. In     order to be affected, a program has to use the `otelhttp.NewHandler` wrapper and not filter any unknown     HTTP methods or User agents on the level of CDN, LB, previous middleware, etc. Version 0.44.0 fixed this     issue when the values collected for attribute `http.request.method` were changed to be restricted to a set     of well-known values and other high cardinality attributes were removed. As a workaround to stop being     affected, `otelhttp.WithFilter()` can be used, but it requires manual careful configuration to not log     certain requests entirely. For convenience and safe usage of this library, it should by default mark with     the label `unknown` non-standard HTTP methods and User agents to show that such requests were made but do     not increase cardinality. In case someone wants to stay with the current behavior, library API should     allow to enable it. (CVE-2023-45142)

  - OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. Prior to version     0.46.0, the grpc Unary Server Interceptor out of the box adds labels `net.peer.sock.addr` and     `net.peer.sock.port` that have unbound cardinality. It leads to the server's potential memory exhaustion     when many malicious requests are sent. An attacker can easily flood the peer address and port for     requests. Version 0.46.0 contains a fix for this issue. As a workaround to stop being affected, a view     removing the attributes can be used. The other possibility is to disable grpc metrics instrumentation by     passing `otelgrpc.WithMeterProvider` option with `noop.NewMeterProvider`. (CVE-2023-47108)

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

The version of amazon-cloudwatch-agent installed on the remote host is prior to 1.300032.3-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2-2024-2424 advisory.

  - A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive     server resource consumption. While the total number of requests is bounded by the     http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create     a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound     the number of simultaneously executing handler goroutines to the stream concurrency limit     (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client     has reset an existing, in-flight request) will be queued until a handler exits. If the request queue grows     too large, the server will terminate the connection. This issue is also fixed in golang.org/x/net/http2     for users manually configuring HTTP/2. The default stream concurrency limit is 250 streams (requests) per     HTTP/2 connection. This value may be adjusted using the golang.org/x/net/http2 package; see the     Server.MaxConcurrentStreams setting and the ConfigureServer function. (CVE-2023-39325)

  - A malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response     body to read many more bytes from the network than are in the body. A malicious HTTP client can further     exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a     handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which     permit including additional metadata in a request or response body sent using the chunked encoding. The     net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large     metadata segment with each byte transferred. The chunk reader now produces an error if the ratio of real     body to encoded bytes grows too small. (CVE-2023-39326)

  - OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. A handler wrapper     out of the box adds labels `http.user_agent` and `http.method` that have unbound cardinality. It leads to     the server's potential memory exhaustion when many malicious requests are sent to it. HTTP header User-     Agent or HTTP method for requests can be easily set by an attacker to be random and long. The library     internally uses `httpconv.ServerRequest` that records every value for HTTP `method` and `User-Agent`. In     order to be affected, a program has to use the `otelhttp.NewHandler` wrapper and not filter any unknown     HTTP methods or User agents on the level of CDN, LB, previous middleware, etc. Version 0.44.0 fixed this     issue when the values collected for attribute `http.request.method` were changed to be restricted to a set     of well-known values and other high cardinality attributes were removed. As a workaround to stop being     affected, `otelhttp.WithFilter()` can be used, but it requires manual careful configuration to not log     certain requests entirely. For convenience and safe usage of this library, it should by default mark with     the label `unknown` non-standard HTTP methods and User agents to show that such requests were made but do     not increase cardinality. In case someone wants to stay with the current behavior, library API should     allow to enable it. (CVE-2023-45142)

  - OpenTelemetry-Go Contrib is a collection of third-party packages for OpenTelemetry-Go. Prior to version     0.46.0, the grpc Unary Server Interceptor out of the box adds labels `net.peer.sock.addr` and     `net.peer.sock.port` that have unbound cardinality. It leads to the server's potential memory exhaustion     when many malicious requests are sent. An attacker can easily flood the peer address and port for     requests. Version 0.46.0 contains a fix for this issue. As a workaround to stop being affected, a view     removing the attributes can be used. The other possibility is to disable grpc metrics instrumentation by     passing `otelgrpc.WithMeterProvider` option with `noop.NewMeterProvider`. (CVE-2023-47108)

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

The remote Redhat Enterprise Linux 8 / 9 host has a package installed that is affected by multiple vulnerabilities as referenced in the RHSA-2024:0207 advisory.

    Red Hat OpenShift Container Platform is Red Hat's cloud computing Kubernetes application platform solution     designed for on-premise or private cloud deployments.

    This advisory contains the RPM packages for Red Hat OpenShift Container Platform 4.14.9. See the following     advisory for the container images for this release:

    https://access.redhat.com/errata/RHSA-2024:0204

    Security Fix(es):

    * cri-o: Pods are able to break out of resource confinement on cgroupv2 (CVE-2023-6476)

    * opentelemetry-go-contrib: DoS vulnerability in otelgrpc due to unbound cardinality metrics     (CVE-2023-47108)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

    All OpenShift Container Platform 4.14 users are advised to upgrade to these updated packages and images     when they are available in the appropriate release channel. To check for available updates, use the     OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at     https://docs.openshift.com/container-platform/4.14/updating/updating_a_cluster/updating-cluster-cli.html

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

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
209193	openSUSE 15 Security Update : etcd (SUSE-SU-2024:3656-1)	Nessus	SuSE Local Security Checks	critical
207218	SUSE SLES15 / openSUSE 15 Security Update : containerd (SUSE-SU-2024:3221-1)	Nessus	SuSE Local Security Checks	critical
206967	SUSE SLES12 Security Update : containerd (SUSE-SU-2024:3188-1)	Nessus	SuSE Local Security Checks	high
201677	CBL Mariner 2.0 Security Update: docker-compose / docker-buildx / moby-containerd-cc / ig / containerd (CVE-2023-47108)	Nessus	MarinerOS Local Security Checks	high
194371	RHEL 8 / 9 : OpenShift Container Platform 4.13.30 (RHSA-2024:0288)	Nessus	Red Hat Local Security Checks	high
191658	Amazon Linux 2 : containerd (ALASECS-2024-035)	Nessus	Amazon Linux Local Security Checks	medium
190049	Amazon Linux 2 : containerd (ALASDOCKER-2024-037)	Nessus	Amazon Linux Local Security Checks	medium
190048	Amazon Linux 2 : containerd (ALASNITRO-ENCLAVES-2024-037)	Nessus	Amazon Linux Local Security Checks	medium
189869	RHEL 8 : OpenShift Container Platform 4.12.48 (RHSA-2024:0489)	Nessus	Red Hat Local Security Checks	high
189868	RHCOS 4 : OpenShift Container Platform 4.12.48 (RHSA-2024:0489)	Nessus	Red Hat Local Security Checks	high
189436	RHCOS 4 : OpenShift Container Platform 4.14.9 (RHSA-2024:0207)	Nessus	Red Hat Local Security Checks	high
189342	Amazon Linux 2023 : amazon-cloudwatch-agent (ALAS2023-2024-498)	Nessus	Amazon Linux Local Security Checks	medium
189333	Amazon Linux 2 : amazon-cloudwatch-agent (ALAS-2024-2424)	Nessus	Amazon Linux Local Security Checks	medium
189173	RHEL 8 / 9 : OpenShift Container Platform 4.14.9 (RHSA-2024:0207)	Nessus	Red Hat Local Security Checks	high

Detections

Analytics

CVE-2023-47108

high

Tenable Plugins

critical

critical

high

high

high

medium

medium

medium

high

high

high

medium

medium

high