CVE-2019-11247

CVE-2019-11247 is a high-severity incorrect authorization vulnerability in k8s.io/apiextensions-apiserver (go), affecting versions >= 0.7.0, < 0.13.9. It is fixed in 0.13.9, 0.14.5, 0.15.2.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Kubernetes kube-apiserver unauthorized access

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.

Impact

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2019-11247 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.13.9, 0.14.5, 0.15.2); upgrading removes the vulnerable code path.

Affected versions

k8s.io/apiextensions-apiserver (>= 0.7.0, < 0.13.9) k8s.io/apiextensions-apiserver (>= 0.14.0, < 0.14.5) k8s.io/apiextensions-apiserver (>= 0.15.0, < 0.15.2)

Security releases

k8s.io/apiextensions-apiserver → 0.13.9 (go) k8s.io/apiextensions-apiserver → 0.14.5 (go) k8s.io/apiextensions-apiserver → 0.15.2 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

k8s.io/apiextensions-apiserver to 0.13.9 or later; k8s.io/apiextensions-apiserver to 0.14.5 or later; k8s.io/apiextensions-apiserver to 0.15.2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2019-11247? CVE-2019-11247 is a high-severity incorrect authorization vulnerability in k8s.io/apiextensions-apiserver (go), affecting versions >= 0.7.0, < 0.13.9. It is fixed in 0.13.9, 0.14.5, 0.15.2. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
  2. How severe is CVE-2019-11247? CVE-2019-11247 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
  3. Which versions of k8s.io/apiextensions-apiserver are affected by CVE-2019-11247? k8s.io/apiextensions-apiserver (go) versions >= 0.7.0, < 0.13.9 is affected.
  4. Is there a fix for CVE-2019-11247? Yes. CVE-2019-11247 is fixed in 0.13.9, 0.14.5, 0.15.2. Upgrade to this version or later.
  5. Is CVE-2019-11247 exploitable, and should I be worried? Whether CVE-2019-11247 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  6. What actually determines whether CVE-2019-11247 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  7. How do I fix CVE-2019-11247?
    • Upgrade k8s.io/apiextensions-apiserver to 0.13.9 or later
    • Upgrade k8s.io/apiextensions-apiserver to 0.14.5 or later
    • Upgrade k8s.io/apiextensions-apiserver to 0.15.2 or later

Stop the waste.
Protect your environment with Kodem.