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

> Authenticated users can escalate privileges to ETCD by exploiting shared Certificate Authority trust between Kubernetes API and ETCD.

- **Severity:** High 8.8 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Mar 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-pw4q-58pr-v79g

## What is CVE-2019-3779?

CVE-2019-3779 is a high-severity vulnerability in Cloud Foundry Container Runtime (CFCR), published on 8 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-264, CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2019-3779?

It affects 1 product.


Products: Cloudfoundry Container Runtime.

## How do I fix CVE-2019-3779?

No fix has been published for CVE-2019-3779 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-3779 being exploited?

There is no known exploitation of CVE-2019-3779 in the wild and no public exploit code.

## Other vulnerabilities in Cloud Foundry Container Runtime (CFCR)

- [CVE-2019-3780](https://insights.sbomify.com/CVE-2019-3780/): Cloud Foundry Container Runtime Leaks IAAS Credentials (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-3779 and fix it if it is affected.

What it is: CVE-2019-3779 is a high-severity vulnerability in Cloud Foundry Container Runtime (CFCR), published on 8 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-3779 in the wild and no public exploit code.

Affected product: Cloud Foundry Container Runtime (CFCR). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-3779/ (Markdown: https://insights.sbomify.com/CVE-2019-3779/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-3779
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-3779
- OSV: https://osv.dev/vulnerability/CVE-2019-3779

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-3779/
Summaries are generated and may contain mistakes; the official description above is the record.