CVE-2018-1002105 Kubernetes priviledge escalation

Bug #1806749 reported by Bruce Jones
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
StarlingX
Fix Released
Medium
Frank Miller

CVE References

Ken Young (kenyis)
tags: added: stx.security
Revision history for this message
Ken Young (kenyis) wrote :

Assigning to Frank Miller, the containers team lead, to plan further how this CVE will be addressed. Given K8s is not part of the main code of Starling X yet, the plan to fix this code is up to the containers team. The ask from the security team is to correct this CVE before the release is complete.

Changed in starlingx:
importance: Undecided → Medium
status: New → Triaged
assignee: nobody → Frank Miller (sensfan22)
tags: added: stx.2019.03
Revision history for this message
Frank Miller (sensfan22) wrote :

We are currently running kubernetes-1.12.1 and the CVE indicates it is addressed in kubernetes-1.12.3. We'll work on identifying when is the right time to up-version to v1.12.3.

Ken Young (kenyis)
tags: added: stx.2019.05
removed: stx.2019.03
Revision history for this message
Frank Miller (sensfan22) wrote :

This was addressed by the following:
https://review.openstack.org/#/c/632548/ (Uprev kubernetes to 1.12.3)

Changed in starlingx:
status: Triaged → Fix Released
Ken Young (kenyis)
tags: added: stx.2.0
removed: stx.2019.05
Ken Young (kenyis)
information type: Private Security → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.