Fixed packages 5
| Release | Package | Fixed in |
|---|---|---|
| Red Hat · OpenShift 4 openshift:4.2::el7 | cri-o | 0:1.14.12-24.dev.rhaos4.2.gita17905f.el7 |
| Red Hat · OpenShift 4 openshift:4.2::el7 | cri-o-debuginfo | 0:1.14.12-24.dev.rhaos4.2.gita17905f.el7 |
| Red Hat · OpenShift 4 openshift:4.2::el8 | cri-o | 0:1.14.12-15.dev.rhaos4.2.gita17905f.el8 |
| Red Hat · OpenShift 4 openshift:4.2::el8 | cri-o-debuginfo | 0:1.14.12-15.dev.rhaos4.2.gita17905f.el8 |
| Red Hat · OpenShift 4 openshift:4.2::el8 | cri-o-debugsource | 0:1.14.12-15.dev.rhaos4.2.gita17905f.el8 |
Vulnerabilities 1
-
Medium 5.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 re…
References
-
article
https://access.redhat.com/security/updates/classification/#moderate
-
report
https://bugzilla.redhat.com/show_bug.cgi?id=1772280
-
advisory
https://security.access.redhat.com/data/csaf/v2/advisories/2020/rhsa-2020_2776.json
-
report
https://access.redhat.com/security/cve/CVE-2019-14891
-
advisory
https://www.cve.org/CVERecord?id=CVE-2019-14891
-
advisory
https://nvd.nist.gov/vuln/detail/CVE-2019-14891
-
article
https://capsule8.com/blog/oomypod-nothin-to-cri-o-bout/