Skip to content
Noroxi
CVE-2019-11249· NVD / CVE Program· CNA kubernetes

kubectl cp allows symlink directory traversal

Noroxi assessment

Priority: Monitor (action score 27/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 3.7% (FIRST EPSS); higher than 89.6% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: atomic-openshift (Red Hat:openshift:3.10::el7) 0:3.10.181-1.git.0.3ab4b3d.el7; atomic-openshift-clients (Red Hat:openshift:3.10::el7) 0:3.10.181-1.git.0.3ab4b3d.el7; atomic-openshift-clients-redistributable (Red Hat:openshift:3.10::el7) 0:3.10.181-1.git.0.3ab4b3d.el7.

Low priority for now. Upgrade to atomic-openshift (Red Hat:openshift:3.10::el7) 0:3.10.181-1.git.0.3ab4b3d.el7; atomic-openshift-clients (Red Hat:openshift:3.10::el7) 0:3.10.181-1.git.0.3ab4b3d.el7; atomic-openshift-clients-redistributable (Red Hat:openshift:3.10::el7) 0:3.10.181-1.git.0.3ab4b3d.el7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

The kubectl cp command allows copying files between containers and the user machine. To copy files from a container, Kubernetes runs tar inside the container to create a tar archive, copies it over the network, and kubectl unpacks it on the user’s machine. If the tar binary in the container is malicious, it could run any code and output unexpected, malicious results. An attacker could use this to write files to any path on the user’s machine when kubectl cp is called, limited only by the system permissions of the local user. 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.1, 1.2, 1.4, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 1.10, 1.11, 1.12.

MediumCVSS 6.5 · v3.1—No exploit Fix available
Published
Aug 28, 2019
Updated
Jun 16, 2026
EPSS
3.7% · 90th percentile

Report tools

JSON

Action score

27

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.7%

CNA vs NVD score

NVD
6.5
CNA · kubernetes
4.8
1.7 point gap

CVSS:3.0/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2019-11249

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Port scanning: 5 full scans a day (members only)
  • Uptime monitoring: 1 site, instant email when it goes down
  • Verify your domain: subdomains and takeover risk scanned every week
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
kuberneteskubernetes
redhatopenshift container platform

Using kubernetes? Add it to your stack and be the first to know about CVEs like this one. (Kubernetes)

Add to my stack

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • kubernetes kubernetes1.0.0 and later · up to 1.12.10 inclusive
  • kubernetes kubernetes1.13.0 and later · before 1.13.9
  • kubernetes kubernetes1.14.0 and later · before 1.14.5
  • kubernetes kubernetes1.15.0 and later · before 1.15.2
  • kubernetes kubernetes1.12.11

Versions reported by the vendor

Affected version ranges reported by the assigning authority (kubernetes). Independent of NVD's CPE analysis and usually ahead of it.

  • Kubernetes Kubernetes

    • prior to 1.13.9, prior to 1.14.5, prior to 1.15.2, 1.1, 1.2, 1.4, 1.5, 1.6, 1.7, 1.8, 1.9, 1.10 … (+2)affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Red Hat:openshift:3.10::el7atomic-openshiftbefore 0:3.10.181-1.git.0.3ab4b3d.el70:3.10.181-1.git.0.3ab4b3d.el7
Red Hat:openshift:3.10::el7atomic-openshift-clientsbefore 0:3.10.181-1.git.0.3ab4b3d.el70:3.10.181-1.git.0.3ab4b3d.el7
Red Hat:openshift:3.10::el7atomic-openshift-clients-redistributablebefore 0:3.10.181-1.git.0.3ab4b3d.el70:3.10.181-1.git.0.3ab4b3d.el7
Red Hat:openshift:3.10::el7atomic-openshift-docker-excluderbefore 0:3.10.181-1.git.0.3ab4b3d.el70:3.10.181-1.git.0.3ab4b3d.el7
Red Hat:openshift:3.10::el7atomic-openshift-excluderbefore 0:3.10.181-1.git.0.3ab4b3d.el70:3.10.181-1.git.0.3ab4b3d.el7
Red Hat:openshift:3.10::el7atomic-openshift-hyperkubebefore 0:3.10.181-1.git.0.3ab4b3d.el70:3.10.181-1.git.0.3ab4b3d.el7
Red Hat:openshift:3.10::el7atomic-openshift-hypershiftbefore 0:3.10.181-1.git.0.3ab4b3d.el70:3.10.181-1.git.0.3ab4b3d.el7
Red Hat:openshift:3.10::el7atomic-openshift-masterbefore 0:3.10.181-1.git.0.3ab4b3d.el70:3.10.181-1.git.0.3ab4b3d.el7
Red Hat:openshift:3.10::el7atomic-openshift-nodebefore 0:3.10.181-1.git.0.3ab4b3d.el70:3.10.181-1.git.0.3ab4b3d.el7
Red Hat:openshift:3.10::el7atomic-openshift-podbefore 0:3.10.181-1.git.0.3ab4b3d.el70:3.10.181-1.git.0.3ab4b3d.el7
Red Hat:openshift:3.10::el7atomic-openshift-sdn-ovsbefore 0:3.10.181-1.git.0.3ab4b3d.el70:3.10.181-1.git.0.3ab4b3d.el7
Red Hat:openshift:3.10::el7atomic-openshift-template-service-brokerbefore 0:3.10.181-1.git.0.3ab4b3d.el70:3.10.181-1.git.0.3ab4b3d.el7
Red Hat:openshift:3.10::el7atomic-openshift-testsbefore 0:3.10.181-1.git.0.3ab4b3d.el70:3.10.181-1.git.0.3ab4b3d.el7
Red Hat:openshift:3.11::el7ansible-service-brokerbefore 1:1.3.23-2.el71:1.3.23-2.el7
Red Hat:openshift:3.11::el7ansible-service-broker-container-scriptsbefore 1:1.3.23-2.el71:1.3.23-2.el7
Red Hat:openshift:3.11::el7ansible-service-broker-selinuxbefore 1:1.3.23-2.el71:1.3.23-2.el7
Red Hat:openshift:3.11::el7automation-broker-apb-rolebefore 1:1.3.23-2.el71:1.3.23-2.el7
Red Hat:openshift:3.9::el7atomic-openshiftbefore 0:3.9.102-1.git.0.6411f52.el70:3.9.102-1.git.0.6411f52.el7
Red Hat:openshift:3.9::el7atomic-openshift-clientsbefore 0:3.9.102-1.git.0.6411f52.el70:3.9.102-1.git.0.6411f52.el7
Red Hat:openshift:3.9::el7atomic-openshift-clients-redistributablebefore 0:3.9.102-1.git.0.6411f52.el70:3.9.102-1.git.0.6411f52.el7
Red Hat:openshift:3.9::el7atomic-openshift-cluster-capacitybefore 0:3.9.102-1.git.0.6411f52.el70:3.9.102-1.git.0.6411f52.el7
Red Hat:openshift:3.9::el7atomic-openshift-docker-excluderbefore 0:3.9.102-1.git.0.6411f52.el70:3.9.102-1.git.0.6411f52.el7
Red Hat:openshift:3.9::el7atomic-openshift-excluderbefore 0:3.9.102-1.git.0.6411f52.el70:3.9.102-1.git.0.6411f52.el7
Red Hat:openshift:3.9::el7atomic-openshift-federation-servicesbefore 0:3.9.102-1.git.0.6411f52.el70:3.9.102-1.git.0.6411f52.el7

+19

Other highest-scoring records for the same primary product.

  • CVE-2018-1002105In all Kubernetes versions prior to v1.10.11, v1.11.5, and v1.12.3, incorrect handling of error responses to proxied upgrade requests in the
    65This week
  • CVE-2019-11248Kubernetes kubelet exposes /debug/pprof info on healthz port
    55Plan
  • CVE-2017-1002101In Kubernetes versions 1.3.x, 1.4.x, 1.5.x, 1.6.x and prior to versions 1.7.14, 1.8.9 and 1.9.4 containers using subpath volume mounts with
    42Plan
  • CVE-2018-1002101In Kubernetes versions 1.9.0-1.9.9, 1.10.0-1.10.5, and 1.11.0-1.11.1, user input was handled insecurely while setting up volume mounts on Wi
    40Plan
  • CVE-2017-1000056Kubernetes version 1.5.0-1.5.4 is vulnerable to a privilege escalation in the PodSecurityPolicy admission plugin resulting in the ability to
    40Plan
  • CVE-2016-1906Openshift allows remote attackers to gain privileges by updating a build configuration that was created with an allowed type to a type that
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
red hat:ansible-service-broker1:1.3.23-2.el7 · Red Hat:openshift:3.11::el7Package registry (OSV)
red hat:ansible-service-broker-container-scripts1:1.3.23-2.el7 · Red Hat:openshift:3.11::el7Package registry (OSV)
red hat:ansible-service-broker-selinux1:1.3.23-2.el7 · Red Hat:openshift:3.11::el7Package registry (OSV)
red hat:atomic-enterprise-service-catalog1:4.1.16-201909090609.git.1.cc4acc1.el7 · Red Hat:openshift:4.1::el7Package registry (OSV)
red hat:atomic-enterprise-service-catalog-svcat1:4.1.16-201909090609.git.1.cc4acc1.el7 · Red Hat:openshift:4.1::el7Package registry (OSV)
red hat:automation-broker-apb-role1:1.3.23-2.el7 · Red Hat:openshift:3.11::el7Package registry (OSV)
red hat:jenkins-2-plugins0:4.1.1567784275-1.el7 · Red Hat:openshift:4.1::el7Package registry (OSV)
red hat:openshift0:4.1.16-201909090609.git.0.2f97059.el7 · Red Hat:openshift:4.1::el7Package registry (OSV)
red hat:openshift-ansible0:4.1.16-201909090609.git.162.a0800db.el7 · Red Hat:openshift:4.1::el7Package registry (OSV)
red hat:openshift-clients0:4.1.16-201909090609.git.0.2f97059.el7 · Red Hat:openshift:4.1::el7Package registry (OSV)
red hat:openshift-clients-redistributable0:4.1.16-201909090609.git.0.2f97059.el7 · Red Hat:openshift:4.1::el7Package registry (OSV)
red hat:openshift-hyperkube0:4.1.16-201909090609.git.0.2f97059.el7 · Red Hat:openshift:4.1::el7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
none
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
None

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records