rpm package
almalinux/toolbox
pkg:rpm/almalinux/toolbox
Vulnerabilities (129)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2021-30465 | Hig | 8.5 | < 0.0.7-1.module_el8.5.0+108+00865455 | 0.0.7-1.module_el8.5.0+108+00865455 | May 27, 2021 | runc before 1.0.0-rc95 allows a Container Filesystem Breakout via Directory Traversal. To exploit the vulnerability, an attacker must be able to create multiple containers with a fairly specific mount configuration. The problem occurs via a symlink-exchange attack that relies on | |
| CVE-2021-20291 | Med | 6.5 | < 0.0.99.3-1.module_el8.5.0+2614+87221ce8 | 0.0.99.3-1.module_el8.5.0+2614+87221ce8 | Apr 1, 2021 | A deadlock vulnerability was found in 'github.com/containers/storage' in versions before 1.28.1. When a container image is processed, each layer is unpacked using `tar`. If one of those layers is not a valid `tar` archive this causes an error leading to an unexpected situation wh | |
| CVE-2021-20188 | Hig | 7.0 | < 0.0.7-1.module_el8.5.0+108+00865455 | 0.0.7-1.module_el8.5.0+108+00865455 | Feb 11, 2021 | A flaw was found in podman before 1.7.0. File permissions for non-root users running in a privileged container are not correctly checked. This flaw can be abused by a low-privileged user inside the container to access any other file in the container, even if owned by the root use | |
| CVE-2020-28851 | Hig | 7.5 | < 0.0.99.3-0.4.module_el8.6.0+2877+8e437bf5 | 0.0.99.3-0.4.module_el8.6.0+2877+8e437bf5 | Jan 2, 2021 | In x/text in Go 1.15.4, an "index out of range" panic occurs in language.ParseAcceptLanguage while parsing the -u- extension. (x/text/language is supposed to be able to parse an HTTP Accept-Language header.) | |
| CVE-2020-28362 | Hig | 7.5 | < 0.0.7-1.module_el8.5.0+108+00865455 | 0.0.7-1.module_el8.5.0+108+00865455 | Nov 18, 2020 | Go before 1.14.12 and 1.15.x before 1.15.4 allows Denial of Service. | |
| CVE-2020-1983 | Hig | 7.5 | < 0.0.7-1.module_el8.5.0+108+00865455 | 0.0.7-1.module_el8.5.0+108+00865455 | Apr 22, 2020 | A use after free vulnerability in ip_reass() in ip_input.c of libslirp 4.2.0 and prior releases allows crafted packets to cause a denial of service. | |
| CVE-2020-10696 | Hig | 8.8 | < 0.0.7-1.module_el8.5.0+108+00865455 | 0.0.7-1.module_el8.5.0+108+00865455 | Mar 31, 2020 | A path traversal flaw was found in Buildah in versions before 1.14.5. This flaw allows an attacker to trick a user into building a malicious container image hosted on an HTTP(s) server and then write files to the user's system anywhere that the user has permissions. | |
| CVE-2019-19921 | Hig | 7.0 | < 0.0.7-1.module_el8.5.0+108+00865455 | 0.0.7-1.module_el8.5.0+108+00865455 | Feb 12, 2020 | runc through 1.0.0-rc9 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. (This vul | |
| CVE-2020-1726 | Med | 5.9 | < 0.0.7-1.module_el8.5.0+108+00865455 | 0.0.7-1.module_el8.5.0+108+00865455 | Feb 11, 2020 | A flaw was discovered in Podman where it incorrectly allows containers when created to overwrite existing files in volumes, even if they are mounted as read-only. When a user runs a malicious container or a container based on a malicious image with an attached volume that is used |
- affected < 0.0.7-1.module_el8.5.0+108+00865455fixed 0.0.7-1.module_el8.5.0+108+00865455
runc before 1.0.0-rc95 allows a Container Filesystem Breakout via Directory Traversal. To exploit the vulnerability, an attacker must be able to create multiple containers with a fairly specific mount configuration. The problem occurs via a symlink-exchange attack that relies on
- affected < 0.0.99.3-1.module_el8.5.0+2614+87221ce8fixed 0.0.99.3-1.module_el8.5.0+2614+87221ce8
A deadlock vulnerability was found in 'github.com/containers/storage' in versions before 1.28.1. When a container image is processed, each layer is unpacked using `tar`. If one of those layers is not a valid `tar` archive this causes an error leading to an unexpected situation wh
- affected < 0.0.7-1.module_el8.5.0+108+00865455fixed 0.0.7-1.module_el8.5.0+108+00865455
A flaw was found in podman before 1.7.0. File permissions for non-root users running in a privileged container are not correctly checked. This flaw can be abused by a low-privileged user inside the container to access any other file in the container, even if owned by the root use
- affected < 0.0.99.3-0.4.module_el8.6.0+2877+8e437bf5fixed 0.0.99.3-0.4.module_el8.6.0+2877+8e437bf5
In x/text in Go 1.15.4, an "index out of range" panic occurs in language.ParseAcceptLanguage while parsing the -u- extension. (x/text/language is supposed to be able to parse an HTTP Accept-Language header.)
- affected < 0.0.7-1.module_el8.5.0+108+00865455fixed 0.0.7-1.module_el8.5.0+108+00865455
Go before 1.14.12 and 1.15.x before 1.15.4 allows Denial of Service.
- affected < 0.0.7-1.module_el8.5.0+108+00865455fixed 0.0.7-1.module_el8.5.0+108+00865455
A use after free vulnerability in ip_reass() in ip_input.c of libslirp 4.2.0 and prior releases allows crafted packets to cause a denial of service.
- affected < 0.0.7-1.module_el8.5.0+108+00865455fixed 0.0.7-1.module_el8.5.0+108+00865455
A path traversal flaw was found in Buildah in versions before 1.14.5. This flaw allows an attacker to trick a user into building a malicious container image hosted on an HTTP(s) server and then write files to the user's system anywhere that the user has permissions.
- affected < 0.0.7-1.module_el8.5.0+108+00865455fixed 0.0.7-1.module_el8.5.0+108+00865455
runc through 1.0.0-rc9 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. (This vul
- affected < 0.0.7-1.module_el8.5.0+108+00865455fixed 0.0.7-1.module_el8.5.0+108+00865455
A flaw was discovered in Podman where it incorrectly allows containers when created to overwrite existing files in volumes, even if they are mounted as read-only. When a user runs a malicious container or a container based on a malicious image with an attached volume that is used
Page 7 of 7