CVE-2019-3782
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 CredHub CLI, versions prior to 2.2.1, inadvertently writes authentication credentials provided via environment variables to its persistent config file. A local authenticated malicious user with access to the CredHub CLI config file can use these credentials to retrieve and modify credentials stored in CredHub that are authorized to the targeted user.
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 CredHub CLI versions prior to 2.2.1 contain a vulnerability where authentication credentials provided via environment variables are inadvertently written to the persistent configuration file on disk. A local authenticated attacker with access to this config file can extract the credentials and use them to retrieve or modify secrets stored in CredHub that are authorized to the compromised user.
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< 2.2.1CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Check installed CredHub CLI versionRun `credhub --version` or `credhub -v` to determine the installed versionAffected if Version is lower than 2.2.1 (e.g., 2.2.0, 2.1.x, etc.)
-
Locate CredHub CLI configuration fileCheck the default config location (typically ~/.credhub/config.yml or similar in the user home directory)Affected if A configuration file exists in the CredHub CLI config directory
-
Inspect config file for stored credentialsExamine the config file contents using a text editor or `cat` command to see if fields like "user", "password", "token", or base64-encoded credentials are persistedAffected if The config file contains any authentication credentials (passwords, tokens, or user identifiers) rather than being empty or only containing non-sensitive settings
-
Verify if environment variable authentication was usedReview shell history or documentation of how CredHub CLI was invoked; check for environment variables like CREDHUB_USER, CREDHUB_PASSWORD, or CREDHUB_TOKEN being set during authenticationAffected if Environment variables were used to provide credentials to CredHub CLI (these get written to the config file in vulnerable versions)
-
Check file permissions on config directoryRun `ls -la` on the CredHub config directory (e.g., ~/.credhub/) to view permissionsAffected if The config file or directory is readable by users other than the owner (permissions are more permissive than 700 or 600)
A user is affected if they use CredHub CLI version lower than 2.2.1 and have a config file that persists credentials that were originally provided via environment variables.
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 data2.2.1
Upgrade CredHub CLI to version 2.2.1 or later, which no longer persists credentials to the config file. Additionally, rotate any credentials that may have been exposed and ensure strict file permissions on the CredHub CLI config directory.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3782 — 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-3782 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