227 lines
15 KiB
JSON
227 lines
15 KiB
JSON
{
|
||
"Definition": [
|
||
{
|
||
"ID": "oval:org.altlinux.errata:def:20221248",
|
||
"Version": "oval:org.altlinux.errata:def:20221248",
|
||
"Class": "patch",
|
||
"Metadata": {
|
||
"Title": "ALT-PU-2022-1248: package `containerd` update to version 1.4.12-alt2",
|
||
"AffectedList": [
|
||
{
|
||
"Family": "unix",
|
||
"Platforms": [
|
||
"ALT Linux branch c9f2"
|
||
],
|
||
"Products": [
|
||
"ALT SPWorkstation",
|
||
"ALT SPServer"
|
||
]
|
||
}
|
||
],
|
||
"References": [
|
||
{
|
||
"RefID": "ALT-PU-2022-1248",
|
||
"RefURL": "https://errata.altlinux.org/ALT-PU-2022-1248",
|
||
"Source": "ALTPU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2021-01907",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2021-01907",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2021-03670",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2021-03670",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2021-04214",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2021-04214",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2022-00757",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2022-00757",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "BDU:2023-00284",
|
||
"RefURL": "https://bdu.fstec.ru/vul/2023-00284",
|
||
"Source": "BDU"
|
||
},
|
||
{
|
||
"RefID": "CVE-2020-15257",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2020-15257",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-21334",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-21334",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-30465",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-30465",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-32760",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-32760",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-41103",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-41103",
|
||
"Source": "CVE"
|
||
},
|
||
{
|
||
"RefID": "CVE-2021-41190",
|
||
"RefURL": "https://nvd.nist.gov/vuln/detail/CVE-2021-41190",
|
||
"Source": "CVE"
|
||
}
|
||
],
|
||
"Description": "This update upgrades containerd to version 1.4.12-alt2. \nSecurity Fix(es):\n\n * BDU:2021-01907: Уязвимость среды выполнения контейнеров Containerd, связанная с отсутствием проверки привилегий контейнеров c UID 0 в том же пространстве имен, что и shim, позволяющая нарушителю получить доступ к конфиденциальным данным и нарушить их целостность\n\n * BDU:2021-03670: Уязвимость конфигурации инструмента для запуска изолированных контейнеров runc, позволяющая нарушителю оказать воздействие на конфиденциальность, целостность и доступность защищаемой информации\n\n * BDU:2021-04214: Уязвимость реализации команды chmod среды выполнения контейнеров Containerd, позволяющая нарушителю повысить свои привилегии\n\n * BDU:2022-00757: Уязвимость среды выполнения контейнеров Containerd, связанная с недостатками разграничения доступа к корневым каталогам и плагинам, позволяющая нарушителю получить доступ на чтение и изменение файлов\n\n * BDU:2023-00284: Уязвимость среды выполнения контейнеров Containerd, связанная с раскрытием информации в ошибочной области данных, позволяющая нарушителю получить доступ к конфиденциальным данным\n\n * CVE-2020-15257: containerd is an industry-standard container runtime and is available as a daemon for Linux and Windows. In containerd before versions 1.3.9 and 1.4.3, the containerd-shim API is improperly exposed to host network containers. Access controls for the shim’s API socket verified that the connecting process had an effective UID of 0, but did not otherwise restrict access to the abstract Unix domain socket. This would allow malicious containers running in the same network namespace as the shim, with an effective UID of 0 but otherwise reduced privileges, to cause new processes to be run with elevated privileges. This vulnerability has been fixed in containerd 1.3.9 and 1.4.3. Users should update to these versions as soon as they are released. It should be noted that containers started with an old version of containerd-shim should be stopped and restarted, as running containers will continue to be vulnerable even after an upgrade. If you are not providing the ability for untrusted users to start containers in the same network namespace as the shim (typically the \"host\" network namespace, for example with docker run --net=host or hostNetwork: true in a Kubernetes pod) and run with an effective UID of 0, you are not vulnerable to this issue. If you are running containers with a vulnerable configuration, you can deny access to all abstract sockets with AppArmor by adding a line similar to deny unix addr=@**, to your policy. It is best practice to run containers with a reduced set of privileges, with a non-zero UID, and with isolated namespaces. The containerd maintainers strongly advise against sharing namespaces with the host. Reducing the set of isolation mechanisms used for a container necessarily increases that container's privilege, regardless of what container runtime is used for running that container.\n\n * CVE-2021-21334: In containerd (an industry-standard container runtime) before versions 1.3.10 and 1.4.4, containers launched through containerd's CRI implementation (through Kubernetes, crictl, or any other pod/container client that uses the containerd CRI service) that share the same image may receive incorrect environment variables, including values that are defined for other containers. If the affected containers have different security contexts, this may allow sensitive information to be unintentionally shared. If you are not using containerd's CRI implementation (through one of the mechanisms described above), you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image which have different environment variables, you are not vulnerable to this issue. If you are not launching multiple containers or Kubernetes pods from the same image in rapid succession, you have reduced likelihood of being vulnerable to this issue This vulnerability has been fixed in containerd 1.3.10 and containerd 1.4.4. Users should update to these versions.\n\n * CVE-2021-30465: 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 a race condition.\n\n * CVE-2021-32760: containerd is a container runtime. A bug was found in containerd versions prior to 1.4.8 and 1.5.4 where pulling and extracting a specially-crafted container image can result in Unix file permission changes for existing files in the host’s filesystem. Changes to file permissions can deny access to the expected owner of the file, widen access to others, or set extended bits like setuid, setgid, and sticky. This bug does not directly allow files to be read, modified, or executed without an additional cooperating process. This bug has been fixed in containerd 1.5.4 and 1.4.8. As a workaround, ensure that users only pull images from trusted sources. Linux security modules (LSMs) like SELinux and AppArmor can limit the files potentially affected by this bug through policies and profiles that prevent containerd from interacting with specific files.\n\n * CVE-2021-41103: containerd is an open source container runtime with an emphasis on simplicity, robustness and portability. A bug was found in containerd where container root directories and some plugins had insufficiently restricted permissions, allowing otherwise unprivileged Linux users to traverse directory contents and execute programs. When containers included executable programs with extended permission bits (such as setuid), unprivileged Linux users could discover and execute those programs. When the UID of an unprivileged Linux user on the host collided with the file owner or group inside a container, the unprivileged Linux user on the host could discover, read, and modify those files. This vulnerability has been fixed in containerd 1.4.11 and containerd 1.5.7. Users should update to these version when they are released and may restart containers or update directory permissions to mitigate the vulnerability. Users unable to update should limit access to the host to trusted users. Update directory permission on container bundles directories.\n\n * CVE-2021-41190: The OCI Distribution Spec project defines an API protocol to facilitate and standardize the distribution of content. In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the absence of an accompanying Content-Type header. If a Content-Type header changed between two pulls of the same digest, a client may interpret the resulting content differently. The OCI Distribution Specification has been updated to require that a mediaType value present in a manifest or index match the Content-Type header used during the push and pull operations. Clients pulling from a registry may distrust the Content-Type header and reject an ambiguous document that contains both “manifests” and “layers” fields or “manifests” and “config” fields if they are unable to update to version 1.0.1 of the spec.",
|
||
"Advisory": {
|
||
"From": "errata.altlinux.org",
|
||
"Severity": "High",
|
||
"Rights": "Copyright 2024 BaseALT Ltd.",
|
||
"Issued": {
|
||
"Date": "2022-02-11"
|
||
},
|
||
"Updated": {
|
||
"Date": "2022-02-11"
|
||
},
|
||
"BDUs": [
|
||
{
|
||
"ID": "BDU:2021-01907",
|
||
"CVSS": "AV:L/AC:L/Au:N/C:P/I:P/A:N",
|
||
"CVSS3": "AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N",
|
||
"CWE": "CWE-669",
|
||
"Href": "https://bdu.fstec.ru/vul/2021-01907",
|
||
"Impact": "Low",
|
||
"Public": "20201119"
|
||
},
|
||
{
|
||
"ID": "BDU:2021-03670",
|
||
"CVSS": "AV:N/AC:M/Au:S/C:C/I:C/A:C",
|
||
"CVSS3": "AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H",
|
||
"CWE": "CWE-22, CWE-59, CWE-367",
|
||
"Href": "https://bdu.fstec.ru/vul/2021-03670",
|
||
"Impact": "High",
|
||
"Public": "20210519"
|
||
},
|
||
{
|
||
"ID": "BDU:2021-04214",
|
||
"CVSS": "AV:N/AC:M/Au:N/C:P/I:P/A:P",
|
||
"CVSS3": "AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L",
|
||
"CWE": "CWE-264, CWE-281, CWE-668",
|
||
"Href": "https://bdu.fstec.ru/vul/2021-04214",
|
||
"Impact": "Low",
|
||
"Public": "20210719"
|
||
},
|
||
{
|
||
"ID": "BDU:2022-00757",
|
||
"CVSS": "AV:L/AC:L/Au:N/C:P/I:P/A:P",
|
||
"CVSS3": "AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
|
||
"CWE": "CWE-22, CWE-276",
|
||
"Href": "https://bdu.fstec.ru/vul/2022-00757",
|
||
"Impact": "Low",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "BDU:2023-00284",
|
||
"CVSS": "AV:N/AC:M/Au:S/C:C/I:N/A:N",
|
||
"CVSS3": "AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N",
|
||
"CWE": "CWE-668",
|
||
"Href": "https://bdu.fstec.ru/vul/2023-00284",
|
||
"Impact": "Low",
|
||
"Public": "20210305"
|
||
}
|
||
],
|
||
"CVEs": [
|
||
{
|
||
"ID": "CVE-2020-15257",
|
||
"CVSS": "AV:L/AC:L/Au:N/C:P/I:P/A:N",
|
||
"CVSS3": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N",
|
||
"CWE": "CWE-669",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2020-15257",
|
||
"Impact": "Low",
|
||
"Public": "20201201"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-21334",
|
||
"CVSS": "AV:N/AC:M/Au:N/C:P/I:N/A:N",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N",
|
||
"CWE": "CWE-668",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-21334",
|
||
"Impact": "Low",
|
||
"Public": "20210310"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-30465",
|
||
"CVSS": "AV:N/AC:M/Au:S/C:P/I:P/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H",
|
||
"CWE": "CWE-362",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-30465",
|
||
"Impact": "High",
|
||
"Public": "20210527"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-32760",
|
||
"CVSS": "AV:N/AC:M/Au:N/C:P/I:P/A:P",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L",
|
||
"CWE": "CWE-732",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-32760",
|
||
"Impact": "Low",
|
||
"Public": "20210719"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-41103",
|
||
"CVSS": "AV:L/AC:L/Au:N/C:C/I:C/A:C",
|
||
"CVSS3": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
|
||
"CWE": "CWE-22",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-41103",
|
||
"Impact": "High",
|
||
"Public": "20211004"
|
||
},
|
||
{
|
||
"ID": "CVE-2021-41190",
|
||
"CVSS": "AV:N/AC:L/Au:S/C:N/I:P/A:N",
|
||
"CVSS3": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:N",
|
||
"CWE": "CWE-843",
|
||
"Href": "https://nvd.nist.gov/vuln/detail/CVE-2021-41190",
|
||
"Impact": "Low",
|
||
"Public": "20211117"
|
||
}
|
||
],
|
||
"AffectedCPEs": {
|
||
"CPEs": [
|
||
"cpe:/o:alt:spworkstation:8.4",
|
||
"cpe:/o:alt:spserver:8.4"
|
||
]
|
||
}
|
||
}
|
||
},
|
||
"Criteria": {
|
||
"Operator": "AND",
|
||
"Criterions": [
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:3001",
|
||
"Comment": "ALT Linux must be installed"
|
||
}
|
||
],
|
||
"Criterias": [
|
||
{
|
||
"Operator": "OR",
|
||
"Criterions": [
|
||
{
|
||
"TestRef": "oval:org.altlinux.errata:tst:20221248001",
|
||
"Comment": "containerd is earlier than 0:1.4.12-alt2"
|
||
}
|
||
]
|
||
}
|
||
]
|
||
}
|
||
}
|
||
]
|
||
} |