ALT-PU-2020-2425-2

Package update cri-o in branch p9

Version1.18.2-alt1

Published2026-02-04

Max severityMEDIUM

Severity:

Closed issues (3)

MEDIUM5.0

A flaw was found in cri-o, as a result of all pod-related processes being placed in the same memory cgroup. This can result in container management (conmon) processes being killed if a workload process triggers an out-of-memory (OOM) condition for the cgroup. An attacker could abuse this flaw to get host network access on an cri-o host.

Published: 2019-11-25Modified: 2024-11-21

CVSS 2.0MEDIUM 6.0

CVSS:2.0/AV:N/AC:M/Au:S/C:P/I:P/A:P

CVSS 3.xMEDIUM 5.0

CVSS:3.x/CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L

References

MEDIUM4.2

An incorrect sysctls validation vulnerability was found in CRI-O 1.18 and earlier. The sysctls from the list of "safe" sysctls specified for the cluster will be applied to the host if an attacker is able to create a pod with a hostIPC and hostNetwork kernel namespace.

Published: 2022-02-09Modified: 2024-11-21

CVSS 2.0MEDIUM 4.9

CVSS:2.0/AV:N/AC:M/Au:S/C:P/I:N/A:P

CVSS 3.xMEDIUM 4.2

CVSS:3.x/CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L

References

GHSA-jqmc-79gx-7g8p

MEDIUM4.2

Incorrect Permission Assignment for Critical Resource in CRI-O

Published: 2022-02-11Modified: 2022-02-24

CVSS 3.xMEDIUM 4.2

CVSS:3.x/CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:L

References