Kubernetes
Approved changes feed: RSS · Atom
cpe:2.3:a:kubernetes:kubernetes:1.14.2:*:*:*:*:*:*:*
part: a version: 1.14.2 update: *
| Vendor | Kubernetes (3ee05930-9e42-51b2-ad52-30832f573b15) |
|---|---|
| Product | Kubernetes (1a2d2535-9ff1-599e-92b3-aa33ed592780) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-11245 |
vulnerable | 2026-06-03 14:39:32.533619 |
kubelet-started container uid changes to root after first restart or if image is already pulled to the node
MEDIUM (4.9)
In kubelet v1.13.6 and v1.14.2, containers for pods that do not specify an explicit runAsUser attempt to run as uid 0 (root) on container restart, or if the image was previously pulled to the node. If the pod specified mustRunAsNonRoot: true, the kubelet will refuse to start the container as root. If the pod did not specify mustRunAsNonRoot: true, the kubelet will run the container as uid 0.
Published: 2019-08-29T00:22:24.173Z
Updated: 2024-09-16T22:09:44.877Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.