CVE-2019-11247: Kubernetes kube-apiserver allows access to custom resources via wrong scope

Published Jul 23, 2019
·
Updated

The Kubernetes API server 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).

Other sources

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.

Affected Software

53 affected componentsFixes available
go/k8s.io/apiextensions-apiserver>=0.15.0<0.15.2
0.15.2
go/k8s.io/apiextensions-apiserver>=0.14.0<0.14.5
0.14.5
go/k8s.io/apiextensions-apiserver>=0.7.0<0.13.9
0.13.9
redhat/atomic-openshift<0:3.10.170-1.git.0.8e592d6.el7
0:3.10.170-1.git.0.8e592d6.el7
redhat/ansible-service-broker<1:1.3.23-2.el7
1:1.3.23-2.el7
redhat/ansible-service-broker<0:1.1.20-2.el7
0:1.1.20-2.el7
redhat/atomic-openshift<0:3.9.101-1.git.0.150f595.el7
0:3.9.101-1.git.0.150f595.el7
redhat/atomic-openshift-descheduler<0:3.9.13-2.git.267.bb59a3f.el7
0:3.9.13-2.git.267.bb59a3f.el7
redhat/atomic-openshift-dockerregistry<0:3.9.101-1.git.1.13625cf.el7
0:3.9.101-1.git.1.13625cf.el7
redhat/atomic-openshift-node-problem-detector<0:3.9.13-2.git.167.5d6b0d4.el7
0:3.9.13-2.git.167.5d6b0d4.el7
redhat/atomic-openshift-web-console<0:3.9.101-1.git.1.601c6d2.el7
0:3.9.101-1.git.1.601c6d2.el7
redhat/cockpit<0:195-2.rhaos.el7
0:195-2.rhaos.el7
redhat/containernetworking-plugins<0:0.5.2-6.el7
0:0.5.2-6.el7
redhat/cri-o<0:1.9.16-3.git858756d.el7
0:1.9.16-3.git858756d.el7
redhat/cri-tools<0:1.0.0-6.rhaos3.9.git8e6013a.el7
0:1.0.0-6.rhaos3.9.git8e6013a.el7
redhat/golang-github-openshift-oauth-proxy<0:2.1-3.git885c9f40.el7
0:2.1-3.git885c9f40.el7
redhat/golang-github-openshift-prometheus-alert-buffer<0:0-3.gitceca8c1.el7
0:0-3.gitceca8c1.el7
redhat/golang-github-prometheus-alertmanager<0:0.14.0-2.git30af4d0.el7
0:0.14.0-2.git30af4d0.el7
redhat/golang-github-prometheus-prometheus<0:2.2.1-2.gitbc6058c.el7
0:2.2.1-2.gitbc6058c.el7
redhat/golang-github-prometheus-promu<0:0-5.git85ceabc.el7
0:0-5.git85ceabc.el7
redhat/hawkular-openshift-agent<0:1.2.2-3.el7
0:1.2.2-3.el7
redhat/heapster<0:1.3.0-4.el7
0:1.3.0-4.el7
redhat/image-inspector<0:2.1.3-2.el7
0:2.1.3-2.el7
redhat/openshift-enterprise-image-registry<0:3.8.0-2.git.216.b6b90bb.el7
0:3.8.0-2.git.216.b6b90bb.el7
redhat/openshift-eventrouter<0:0.1-3.git5bd9251.el7
0:0.1-3.git5bd9251.el7
redhat/openshift-external-storage<0:0.0.1-9.git78d6339.el7
0:0.0.1-9.git78d6339.el7
redhat/openvswitch-ovn-kubernetes<0:0.1.0-3.el7
0:0.1.0-3.el7
redhat/openshift<0:4.1.10-201908060758.git.0.d81afa6.el8
0:4.1.10-201908060758.git.0.d81afa6.el8
redhat/kubernetes<1.13.9
1.13.9
redhat/kubernetes<1.14.5
1.14.5
redhat/kubernetes<1.15.2
1.15.2
redhat/kubernetes<1.16.0
1.16.0
Kubernetes kubernetes>=1.7.0<=1.12.10
Kubernetes kubernetes>=1.13.0<1.13.9
Kubernetes kubernetes>=1.14.0<1.14.5
Kubernetes kubernetes>=1.15.0<1.15.2
Kubernetes kubernetes=1.12.11-beta0
redhat OpenShift Container Platform=3.9
redhat OpenShift Container Platform=3.10
redhat OpenShift Container Platform=3.11
IBM Edge Application Manager<=4.5
alpine/k3s<0.8.0-r0
0.8.0-r0
alpine/k3s<0.8.0-r0
0.8.0-r0
alpine/k3s<0.8.0-r0
0.8.0-r0
alpine/k3s<0.8.0-r0
0.8.0-r0
alpine/k3s<0.8.0-r0
0.8.0-r0
alpine/k3s<0.8.0-r0
0.8.0-r0
alpine/k3s<0.8.0-r0
0.8.0-r0
alpine/k3s<0.8.0-r0
0.8.0-r0
alpine/k3s<0.8.0-r0
0.8.0-r0
alpine/k3s<0.8.0-r0
0.8.0-r0
alpine/k3s<0.8.0-r0
0.8.0-r0
alpine/k3s<0.8.0-r0
0.8.0-r0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade go/k8s.io/apiextensions-apiserver to a version that resolves this vulnerability.

    Fixed in 0.15.2
  2. Upgrade

    Upgrade go/k8s.io/apiextensions-apiserver to a version that resolves this vulnerability.

    Fixed in 0.14.5
  3. Upgrade

    Upgrade go/k8s.io/apiextensions-apiserver to a version that resolves this vulnerability.

    Fixed in 0.13.9
  4. Upgrade

    Upgrade redhat/atomic-openshift to a version that resolves this vulnerability.

    Fixed in 0:3.10.170-1.git.0.8e592d6.el7
  5. Upgrade

    Upgrade redhat/ansible-service-broker to a version that resolves this vulnerability.

    Fixed in 1:1.3.23-2.el7
  6. Upgrade

    Upgrade redhat/ansible-service-broker to a version that resolves this vulnerability.

    Fixed in 0:1.1.20-2.el7
  7. Upgrade

    Upgrade redhat/atomic-openshift to a version that resolves this vulnerability.

    Fixed in 0:3.9.101-1.git.0.150f595.el7
  8. Upgrade

    Upgrade redhat/atomic-openshift-descheduler to a version that resolves this vulnerability.

    Fixed in 0:3.9.13-2.git.267.bb59a3f.el7
  9. Upgrade

    Upgrade redhat/atomic-openshift-dockerregistry to a version that resolves this vulnerability.

    Fixed in 0:3.9.101-1.git.1.13625cf.el7
  10. Upgrade

    Upgrade redhat/atomic-openshift-node-problem-detector to a version that resolves this vulnerability.

    Fixed in 0:3.9.13-2.git.167.5d6b0d4.el7
  11. Upgrade

    Upgrade redhat/atomic-openshift-web-console to a version that resolves this vulnerability.

    Fixed in 0:3.9.101-1.git.1.601c6d2.el7
  12. Upgrade

    Upgrade redhat/cockpit to a version that resolves this vulnerability.

    Fixed in 0:195-2.rhaos.el7
  13. Upgrade

    Upgrade redhat/containernetworking-plugins to a version that resolves this vulnerability.

    Fixed in 0:0.5.2-6.el7
  14. Upgrade

    Upgrade redhat/cri-o to a version that resolves this vulnerability.

    Fixed in 0:1.9.16-3.git858756d.el7
  15. Upgrade

    Upgrade redhat/cri-tools to a version that resolves this vulnerability.

    Fixed in 0:1.0.0-6.rhaos3.9.git8e6013a.el7
  16. Upgrade

    Upgrade redhat/golang-github-openshift-oauth-proxy to a version that resolves this vulnerability.

    Fixed in 0:2.1-3.git885c9f40.el7
  17. Upgrade

    Upgrade redhat/golang-github-openshift-prometheus-alert-buffer to a version that resolves this vulnerability.

    Fixed in 0:0-3.gitceca8c1.el7
  18. Upgrade

    Upgrade redhat/golang-github-prometheus-alertmanager to a version that resolves this vulnerability.

    Fixed in 0:0.14.0-2.git30af4d0.el7
  19. Upgrade

    Upgrade redhat/golang-github-prometheus-prometheus to a version that resolves this vulnerability.

    Fixed in 0:2.2.1-2.gitbc6058c.el7
  20. Upgrade

    Upgrade redhat/golang-github-prometheus-promu to a version that resolves this vulnerability.

    Fixed in 0:0-5.git85ceabc.el7
  21. Upgrade

    Upgrade redhat/hawkular-openshift-agent to a version that resolves this vulnerability.

    Fixed in 0:1.2.2-3.el7
  22. Upgrade

    Upgrade redhat/heapster to a version that resolves this vulnerability.

    Fixed in 0:1.3.0-4.el7
  23. Upgrade

    Upgrade redhat/image-inspector to a version that resolves this vulnerability.

    Fixed in 0:2.1.3-2.el7
  24. Upgrade

    Upgrade redhat/openshift-enterprise-image-registry to a version that resolves this vulnerability.

    Fixed in 0:3.8.0-2.git.216.b6b90bb.el7
  25. Upgrade

    Upgrade redhat/openshift-eventrouter to a version that resolves this vulnerability.

    Fixed in 0:0.1-3.git5bd9251.el7
  26. Upgrade

    Upgrade redhat/openshift-external-storage to a version that resolves this vulnerability.

    Fixed in 0:0.0.1-9.git78d6339.el7
  27. Upgrade

    Upgrade redhat/openvswitch-ovn-kubernetes to a version that resolves this vulnerability.

    Fixed in 0:0.1.0-3.el7
  28. Upgrade

    Upgrade redhat/openshift to a version that resolves this vulnerability.

    Fixed in 0:4.1.10-201908060758.git.0.d81afa6.el8
  29. Upgrade

    Upgrade redhat/kubernetes to a version that resolves this vulnerability.

    Fixed in 1.13.9
  30. Upgrade

    Upgrade redhat/kubernetes to a version that resolves this vulnerability.

    Fixed in 1.14.5
  31. Upgrade

    Upgrade redhat/kubernetes to a version that resolves this vulnerability.

    Fixed in 1.15.2
  32. Upgrade

    Upgrade redhat/kubernetes to a version that resolves this vulnerability.

    Fixed in 1.16.0
  33. Upgrade

    Upgrade alpine/k3s to a version that resolves this vulnerability.

    Fixed in 0.8.0-r0
  34. Upgrade

    Upgrade Kubernetes kube-apiserver to a version that resolves this vulnerability.

    Fixed in 1.15.2

Event History

Aug 5, 2019
CVE Published
12:00 AM
Aug 29, 2019
CVE Published
via MITRE·12:25 AM
Data Sourced
via MITRE·12:25 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:15 AM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·01:15 AM
DescriptionSeverityAffected Software
May 24, 2022
Advisory Published
04:55 PM
Aug 20, 2025
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is CVE-2019-11247?

CVE-2019-11247 is a vulnerability in the Kubernetes kube-apiserver that allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced.

2

How severe is CVE-2019-11247?

CVE-2019-11247 has a severity rating of 8.1, which is considered high.

3

What software is affected by CVE-2019-11247?

Kubernetes versions between 1.7.0 and 1.12.10, 1.13.0 and 1.13.9, and 1.14.0 and 1.14.5 are affected by CVE-2019-11247, as well as Redhat Openshift Container Platform 3.9, 3.10, and 3.11.

4

What is the remedy for CVE-2019-11247?

To fix CVE-2019-11247, users should update to k8s.io/apiextensions-apiserver version 0.15.2, 0.14.5, or 0.13.9 depending on the affected Kubernetes version.

5

Where can I find more information about CVE-2019-11247?

More information about CVE-2019-11247 can be found on the CVE website (https://www.cve.org/CVERecord?id=CVE-2019-11247), NIST National Vulnerability Database (https://nvd.nist.gov/vuln/detail/CVE-2019-11247), and Redhat Bugzilla (https://bugzilla.redhat.com/show_bug.cgi?id=1732192).

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203