CVE-2019-3779
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCloud 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCloud Foundry Container Runtime versions prior to 0.29.0 deploy Kubernetes clusters using a single CA to sign certificates for both the Kubernetes API server and ETCD. An authenticated cluster user can abuse the Kubernetes CSR (Certificate Signing Request) mechanism to obtain a certificate signed by this shared CA, then use it to authenticate to ETCD with elevated privileges, bypassing separation between Kubernetes and ETCD trust boundaries.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.29.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Cloud Foundry Container Runtime is deployedReview your environment inventory or deployment documentation to determine if CFCR (also known as Garden Container Runtime) is being used to manage Kubernetes clustersAffected if CFCR is not present in the environment, this CVE does not apply
-
Determine the installed CFCR versionQuery the CFCR components or deployment metadata to retrieve the version number; compare it against the affected range of versions prior to 0.29.0Affected if The installed version is 0.29.0 or later, the vulnerability has been patched; if the version is unknown or prior to 0.29.0, proceed to the next check
-
Inspect the CA certificate configuration for Kubernetes API and ETCDExamine the certificate authority configuration files or certificate bundles used during cluster setup; verify whether a single CA is being used to sign both Kubernetes API server and ETCD certificates, or if separate CAs are configuredAffected if A single shared CA is used to sign certificates for both the Kubernetes API server and ETCD, the vulnerable condition exists; separate CAs indicate the mitigation is in place
The environment is affected if Cloud Foundry Container Runtime is deployed with a version prior to 0.29.0 using a single CA for both Kubernetes API server and ETCD certificates.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data0.29.0
Upgrade Cloud Foundry Container Runtime to version 0.29.0 or later, which implements separate CAs for Kubernetes API and ETCD. If upgrading is not immediately possible, implement network-level restrictions on ETCD access and monitor for unauthorized certificate requests.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3779 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-3779 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data