CVE-2020-5400
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 Cloud Controller (CAPI), versions prior to 1.91.0, logs properties of background jobs when they are run, which may include sensitive information such as credentials if provided to the job. A malicious user with access to those logs may gain unauthorized access to resources protected by such credentials.
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 confidenceThe Cloud Foundry Cloud Controller (CAPI) logs the properties of background jobs when they execute. If credentials are passed as parameters to these jobs, they are written to logs in plaintext. A user with access to those logs can retrieve the credentials and gain unauthorized access to protected resources.
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< 1.91.0< 12.33.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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Determine installed CAPI Release versionRun 'bosh -d DEPLOYMENT_NAME releases' to list installed releases, or check the deployment manifest for the capi job versionAffected if The CAPI Release version is below 1.91.0
-
Determine installed CF Deployment versionRun 'bosh -d DEPLOYMENT_NAME releases' to list the cf-deployment release, or check the deployment manifest for the cf-deployment version tagAffected if The CF Deployment version is below 12.33.0
-
Search logs for plaintext credentialsExamine Cloud Controller logs (typically in /var/vcap/sys/log/cloud_controller_ng/ or via 'bosh logs cloud_controller_ng') for patterns matching credentials, API keys, tokens, or passwords in plaintext. Search for strings like 'password=', 'secret=', 'token=', 'api_key=' appearing in log entries related to job executionAffected if Log entries contain plaintext credentials or sensitive parameters passed to background jobs
-
Verify log access controlsReview who has read access to the Cloud Controller log files and log aggregation systems. Check file permissions on /var/vcap/sys/log/ and review access to any centralized logging infrastructure (such as Splunk, ELK, or syslog destinations)Affected if Broad or unaudited access exists to logs containing job execution details
You are affected if your CAPI Release is below 1.91.0 or CF Deployment is below 12.33.0 AND plaintext credentials appear in Cloud Controller logs accessible to unauthorized users.
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 data1.91.012.33.0
Upgrade CAPI to version 1.91.0 or later to prevent sensitive data from being logged. Audit logs for exposed credentials, revoke and rotate any credentials that may have been disclosed, and review log access controls to limit exposure.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5400 — 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-2020-5400 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