Detections
Analytics
Alibaba Cloud Linux 3 : 0050: container-tools:rhel8 (ALINUX3-SA-2024:0050)
critical Nessus Plugin ID 236060
Synopsis
The remote Alibaba Cloud Linux host is missing one or more security updates.Description
The remote Alibaba Cloud Linux 3 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALINUX3-SA-2024:0050 advisory.Package updates are available for Alibaba Cloud Linux 3 that fix the following vulnerabilities:
CVE-2022-27191:
The golang.org/x/crypto/ssh package before 0.0.0-20220314234659-1baeb1ce4c0b for Go allows an attacker to crash a server in certain circumstances involving AddHostKey.
CVE-2022-2989:
An incorrect handling of the supplementary groups in the Podman container engine might lead to the 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-3064:
Parsing malicious or large YAML documents can consume excessive amounts of CPU or memory.
CVE-2022-41723:
A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.
CVE-2022-41724:
Large handshake records may cause panics in crypto/tls. Both clients and servers may send large TLS handshake records which cause servers and clients, respectively, to panic when attempting to construct responses. This affects all TLS 1.3 clients, TLS 1.2 clients which explicitly enable session resumption (by setting Config.ClientSessionCache to a non-nil value), and TLS 1.3 servers which request client certificates (by setting Config.ClientAuth >= RequestClientCert).
CVE-2022-41725:
A denial of service is possible from excessive resource consumption in net/http and mime/multipart.
Multipart form parsing with mime/multipart.Reader.ReadForm can consume largely unlimited amounts of memory and disk files. This also affects form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. ReadForm takes a maxMemory parameter, and is documented as storing up to maxMemory bytes +10MB (reserved for non-file parts) in memory. File parts which cannot be stored in memory are stored on disk in temporary files. The unconfigurable 10MB reserved for non-file parts is excessively large and can potentially open a denial of service vector on its own. However, ReadForm did not properly account for all memory consumed by a parsed form, such as map entry overhead, part names, and MIME headers, permitting a maliciously crafted form to consume well over 10MB. In addition, ReadForm contained no limit on the number of disk files created, permitting a relatively small request body to create a large number of disk temporary files. With fix, ReadForm now properly accounts for various forms of memory overhead, and should now stay within its documented limit of 10MB + maxMemory bytes of memory consumption. Users should still be aware that this limit is high and may still be hazardous. In addition, ReadForm now creates at most one on-disk temporary file, combining multiple form parts into a single temporary file. The mime/multipart.File interface type's documentation states, If stored on disk, the File's underlying concrete type will be an *os.File.. This is no longer the case when a form contains more than one file part, due to this coalescing of parts into a single file. The previous behavior of using distinct files for each form part may be reenabled with the environment variable GODEBUG=multipartfiles=distinct. Users should be aware that multipart.ReadForm and the http.Request methods that call it do not limit the amount of disk consumed by temporary files. Callers can limit the size of form data with http.MaxBytesReader.
CVE-2023-24534:
HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service. Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.
With fix, header parsing now correctly allocates only the memory required to hold parsed headers.
CVE-2023-24536:
Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3.
ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service.
This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=.
CVE-2023-24537:
Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow.
CVE-2023-24538:
Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. var a = {{.}}), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml. With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21. Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution.
CVE-2023-24539:
Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.
CVE-2023-24540:
Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set \t\n\f\r\u0020\u2028\u2029 in JavaScript contexts that also contain actions may not be properly sanitized during execution.
CVE-2023-25173:
containerd is an open source container runtime. A bug was found in containerd prior to versions 1.6.18 and 1.5.18 where supplementary groups are not set up properly inside a container. If an attacker has direct access to a container and manipulates their supplementary group access, they may be able to use supplementary group access to bypass primary group restrictions in some cases, potentially gaining access to sensitive information or gaining the ability to execute code in that container. Downstream applications that use the containerd client library may be affected as well.
This bug has been fixed in containerd v1.6.18 and v.1.5.18. Users should update to these versions and recreate containers to resolve this issue. Users who rely on a downstream application that uses containerd's client library should check that application for a separate advisory and instructions. As a workaround, ensure that the `USER $USERNAME` Dockerfile instruction is not used. Instead, set the container entrypoint to a value similar to `ENTRYPOINT [su, -, user]` to allow `su` to properly set up supplementary groups.
CVE-2023-25809:
runc is a CLI tool for spawning and running containers according to the OCI specification. In affected versions it was found that rootless runc makes `/sys/fs/cgroup` writable in following conditons: 1. when runc is executed inside the user namespace, and the `config.json` does not specify the cgroup namespace to be unshared (e.g.., `(docker|podman|nerdctl) run --cgroupns=host`, with Rootless Docker/Podman/nerdctl) or 2. when runc is executed outside the user namespace, and `/sys` is mounted with `rbind, ro` (e.g., `runc spec --rootless`; this condition is very rare). A container may gain the write access to user-owned cgroup hierarchy `/sys/fs/cgroup/user.slice/...` on the host . Other users's cgroup hierarchies are not affected.
Users are advised to upgrade to version 1.1.5. Users unable to upgrade may unshare the cgroup namespace (`(docker|podman|nerdctl) run --cgroupns=private)`. This is the default behavior of Docker/Podman/nerdctl on cgroup v2 hosts. or add `/sys/fs/cgroup` to `maskedPaths`.
CVE-2023-27561:
runc through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with custom volume-mount configurations, and be able to run custom images. NOTE: this issue exists because of a CVE-2019-19921 regression.
CVE-2023-28642:
runc is a CLI tool for spawning and running containers according to the OCI specification. It was found that AppArmor can be bypassed when `/proc` inside the container is symlinked with a specific mount configuration. This issue has been fixed in runc version 1.1.5, by prohibiting symlinked `/proc`. See PR #3785 for details. users are advised to upgrade. Users unable to upgrade should avoid using an untrusted container image.
CVE-2023-29400:
Templates containing actions in unquoted HTML attributes (e.g. attr={{.}}) executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.
CVE-2023-29406:
The HTTP/1 client does not fully validate the contents of the Host header. A maliciously crafted Host header can inject additional headers or entire requests. With fix, the HTTP/1 client now refuses to send requests containing an invalid Request.Host or Request.URL.Host value.
CVE-2023-3978:
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-2022-1227:
A privilege escalation flaw was found in Podman. This flaw allows an attacker to publish a malicious image to a public registry. Once this image is downloaded by a potential victim, the vulnerability is triggered after a user runs the 'podman top' command. This action gives the attacker access to the host filesystem, leading to information disclosure or denial of service.
CVE-2022-21698:
client_golang is the instrumentation library for Go applications in Prometheus, and the promhttp package in client_golang provides tooling around HTTP servers and clients. In client_golang prior to version 1.11.1, HTTP server is susceptible to a Denial of Service through unbounded cardinality, and potential memory exhaustion, when handling requests with non-standard HTTP methods. In order to be affected, an instrumented software must use any of `promhttp.InstrumentHandler*` middleware except `RequestsInFlight`;
not filter any specific methods (e.g GET) before middleware; pass metric with `method` label name to our middleware; and not have any firewall/LB/proxy that filters away requests with unknown `method`.
client_golang version 1.11.1 contains a patch for this issue. Several workarounds are available, including removing the `method` label name from counter/gauge used in the InstrumentHandler; turning off affected promhttp handlers; adding custom middleware before promhttp handler that will sanitize the request method given by Go http.Request; and using a reverse proxy or web application firewall, configured to only allow a limited set of methods.
CVE-2022-27650:
A flaw was found in crun where containers were incorrectly started with non-empty default permissions. A vulnerability was found in Moby (Docker Engine) where containers were started incorrectly with non-empty inheritable Linux process capabilities. This flaw allows an attacker with access to programs with inheritable file capabilities to elevate those capabilities to the permitted set when execve(2) runs.
CVE-2024-21626:
runc is a CLI tool for spawning and running containers on Linux according to the OCI specification. In runc 1.1.11 and earlier, due to an internal file descriptor leak, an attacker could cause a newly-spawned container process (from runc exec) to have a working directory in the host filesystem namespace, allowing for a container escape by giving access to the host filesystem (attack 2). The same attack could be used by a malicious image to allow a container process to gain access to the host filesystem through runc run (attack 1). Variants of attacks 1 and 2 could be also be used to overwrite semi-arbitrary host binaries, allowing for complete container escapes (attack 3a and attack 3b). runc 1.1.12 includes patches for this issue.
Tenable has extracted the preceding description block directly from the Alibaba Cloud 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.
Solution
Update the affected packages.See Also
http://mirrors.aliyun.com/alinux/3/cve/alinux3-sa-20240050.xml
Plugin Details
Severity: Critical
ID: 236060
File Name: alinux3_sa_2024-0050.nasl
Version: 1.1
Type: local
Published: 5/14/2025
Updated: 5/14/2025
Supported Sensors: Nessus
Risk Information
VPR
Risk Factor: Critical
Score: 9.2
CVSS v2
Risk Factor: Medium
Base Score: 6.8
Temporal Score: 5.6
Vector: CVSS2#AV:N/AC:M/Au:N/C:P/I:P/A:P
CVSS Score Source: CVE-2022-1227
CVSS v3
Risk Factor: Critical
Base Score: 9.8
Temporal Score: 9.1
Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Temporal Vector: CVSS:3.0/E:F/RL:O/RC:C
CVSS Score Source: CVE-2023-24540
CVSS v4
Risk Factor: Critical
Base Score: 9.3
Threat Score: 8.9
Threat Vector: CVSS:4.0/E:P
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CVSS Score Source: CVE-2023-3978
Vulnerability Information
CPE: p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:oci-seccomp-bpf-hook-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:criu-debugsource, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:podman-remote-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:podman-gvproxy, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:runc-debugsource, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:podman-gvproxy-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:containernetworking-plugins-debugsource, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:podman-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:skopeo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:buildah-debugsource, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:fuse-overlayfs, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:crit, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:python3-criu, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:crun-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:toolbox-debugsource, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:slirp4netns, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:podman, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:criu, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:podman-remote, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:podman-catatonit-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:skopeo-tests, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:crun-debugsource, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:buildah-tests-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:conmon-debugsource, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:conmon, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:crun, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:runc-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:python3-podman, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:podman-catatonit, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:slirp4netns-debugsource, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:containers-common, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:conmon-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:buildah, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:toolbox, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:container-selinux, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:containernetworking-plugins, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:oci-seccomp-bpf-hook-debugsource, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:criu-libs-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:criu-devel, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:criu-libs, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:fuse-overlayfs-debugsource, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:oci-seccomp-bpf-hook, cpe:/o:alibabacloud:alibaba_cloud_linux_3, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:podman-plugins-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:podman-debugsource, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:buildah-tests, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:buildah-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:runc, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:toolbox-tests, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:criu-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:slirp4netns-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:containernetworking-plugins-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:fuse-overlayfs-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:toolbox-debuginfo, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:cockpit-podman, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:podman-docker, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:podman-tests, p-cpe:/a:alibabacloud:alibaba_cloud_linux_3:podman-plugins
Required KB Items: Host/local_checks_enabled, Host/cpu, Host/Alibaba/release, Host/Alibaba/rpm-list
Exploit Available: true
Exploit Ease: Exploits are available
Patch Publication Date: 4/12/2024
Vulnerability Publication Date: 2/15/2022
Reference Information
CVE: CVE-2022-1227, CVE-2022-21698, CVE-2022-27191, CVE-2022-27650, CVE-2022-2989, CVE-2022-3064, CVE-2022-41723, CVE-2022-41724, CVE-2022-41725, CVE-2023-24534, CVE-2023-24536, CVE-2023-24537, CVE-2023-24538, CVE-2023-24539, CVE-2023-24540, CVE-2023-25173, CVE-2023-25809, CVE-2023-27561, CVE-2023-28642, CVE-2023-29400, CVE-2023-29406, CVE-2023-3978, CVE-2024-21626