Improper Access Control Affecting cri-o package, versions <0:1.9.16-3.git858756d.el7


Severity

Recommended
high

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.34% (73rd percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Improper Access Control vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-RHEL7-CRIO-5254323
  • published26 Mar 2023
  • disclosed5 Aug 2019

Introduced: 5 Aug 2019

CVE-2019-11247  (opens in a new tab)
CWE-284  (opens in a new tab)

How to fix?

Upgrade RHEL:7 cri-o to version 0:1.9.16-3.git858756d.el7 or higher.
This issue was patched in RHSA-2019:2769.

NVD Description

Note: Versions mentioned in the description apply only to the upstream cri-o package and not the cri-o package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced. Authorizations for the resource accessed in this manner are enforced using roles and role bindings within the namespace, meaning that a user with access only to a resource in one namespace could create, view update or delete the cluster-scoped resource (according to their namespace role privileges). Kubernetes affected versions include versions prior to 1.13.9, versions prior to 1.14.5, versions prior to 1.15.2, and versions 1.7, 1.8, 1.9, 1.10, 1.11, 1.12.

CVSS Scores

version 3.1