CVE-2019-3780
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.28.0, deploys K8s worker nodes that contains a configuration file with IAAS credentials. A malicious user with access to the k8s nodes can obtain IAAS credentials allowing the user to escalate privileges to gain access to the IAAS account.
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.28.0 deploy Kubernetes worker nodes that contain a configuration file with plaintext IAAS credentials. A malicious user with access to these k8s nodes can retrieve the credentials and escalate privileges to access the underlying IAAS account.
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.28.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.1/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 deployedCheck for the presence of Cloud Foundry Container Runtime (CFR) components in your environment. Look for CFR-specific deployments, namespaces, or documentation indicating its use.Affected if CFR is deployed in the environment
-
Check the CFR versionRun the command to retrieve the installed Cloud Foundry Container Runtime version. This may be found in the CFR deployment metadata, BOSH release information, or via 'bosh releases' if using BOSH. Compare the version number to the affected range.Affected if The installed version is prior to 0.28.0 (e.g., 0.27.x, 0.26.x, etc.)
-
Access Kubernetes worker nodesUse your existing access mechanisms (e.g., BOSH ssh, kubectl debug, or cloud provider console) to access the Kubernetes worker nodes provisioned by CFR.Affected if You can access the k8s worker nodes
-
Locate the configuration file with plaintext IAAS credentialsOn each worker node, search common configuration directories for files that may contain cloud provider credentials. Look for plaintext credential files in locations such as the kubelet config directory, cloud-provider configuration paths, or IAAS-specific config directories. Use commands like 'find' or 'ls' to locate configuration files.Affected if A configuration file exists on the worker node containing plaintext IAAS credentials (e.g., AWS keys, Azure service principal, GCP service account json)
-
Inspect credential file contentsExamine the identified configuration file using 'cat' or a text editor to verify the credentials are stored in plaintext (not encrypted or hashed).Affected if The file contains unencrypted, plaintext IAAS credentials
You are affected if Cloud Foundry Container Runtime versions prior to 0.28.0 are deployed AND plaintext IAAS credentials are found in a configuration file on the Kubernetes worker nodes.
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.28.0
Upgrade to Cloud Foundry Container Runtime version 0.28.0 or later to remediate. Additionally, rotate any IAAS credentials that may have been exposed as a precaution.
- Consultation6.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3780 — 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-3780 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