Cloud Foundry Container Runtime allows a user to bypass security policy when talking to ETCD

published 2019-03-08 7y ago modified 2026-06-17 4mo ago also EUVD-2019-13410

cvss: 8.8; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits: 0; none known

Cloud Foundry Container Runtime, versions prior to 0.29.0, deploys Kubernetes clusters utilize the same CA (Certificate Authority) to sign and trust certs for ETCD as used by the Kubernetes API. This could allow a user authenticated with a cluster to request a signed certificate leveraging the Kubernetes CSR capability to obtain a credential that could escalate privilege access to ETCD.

Patch / fix

fixed in 1

Cloud Foundry Cloud Foundry Container Runtime (CFCR) v0.29.0

Is CVE-2019-3779 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.67% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	3.0	8.8	CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD	3.0	8.8	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	4.0	AV:N/AC:L/Au:S/C:P/I:N/A:N

Affected products

Cloud Foundry Cloud Foundry Container Runtime (CFCR)

Classification

Weakness

CWE-284 Improper Access Control
CWE-264 Permissions, Privileges, and Access Controls

References

cloudfoundry.org /blog/cve-2019-3779
vendor-advisory

Sources

CVE List CVE-2019-3779
NVD CVE-2019-3779

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.