CVE-2019-3801
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 cf-deployment, versions prior to 7.9.0, contain java components that are using an insecure protocol to fetch dependencies when building. A remote unauthenticated malicious attacker could hijack the DNS entry for the dependency, and inject malicious code into the component.
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 · moderate confidenceJava components in Cloud Foundry cf-deployment versions prior to 7.9.0 use insecure protocols (likely HTTP) to fetch dependencies during the build process. A remote unauthenticated attacker could hijack the DNS entry for the dependency server and perform a man-in-the-middle attack to inject malicious code into the downloaded dependencies.
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< 7.9.0>= 1.9, < 1.9.10>= 2.1, < 2.1.3< 64.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 cf-deployment versionRun 'bosh -d <deployment> env' or check your cf-deployment manifest/ops-files for the release version. If using 'cf-deployment' repo, check the version tag or commit.Affected if The installed cf-deployment version is prior to 7.9.0
-
Check Credhub versionRun 'bosh -d credhub env' or query the Credhub release version via 'bosh releases' and note the version number.Affected if Credhub version is 1.9.x (where x < 10) or 2.1.x (where x < 3)
-
Check UAA Release versionRun 'bosh -d uaa env' or query the UAA release version via 'bosh releases'. Check the release name and version deployed.Affected if UAA Release version is less than 64.0
-
Verify dependency fetch configuration (optional)Inspect your build pipelines or CI/CD configurations that use these components. Look for any references to HTTP URLs when fetching Java dependencies.Affected if Build processes use HTTP instead of HTTPS for dependency retrieval
You are affected if any of your deployed cf-deployment is before 7.9.0, Credhub is 1.9.x before 10 or 2.1.x before 3, or UAA Release is before 64.0, and your build process fetches dependencies over insecure protocols.
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.
dbcve · scoped1.9.102.1.37.9.0
Upgrade cf-deployment to version 7.9.0 or later, which addresses the insecure dependency fetching. Additionally, audit all build processes to ensure HTTPS is used for all dependency downloads.
cf-deployment 7.9.0; Credhub 1.9.10 or 2.1.3; UAA Release 64.0
- Upgrade cf-deployment to version 7.9.0 or later
- If using Credhub 1.9.x, upgrade to version 1.9.10 or later
- If using Credhub 2.1.x, upgrade to version 2.1.3 or later
- Upgrade UAA Release to version 64.0 or later
- After upgrading, verify that all dependency downloads now use secure protocols (HTTPS)
- Redeploy the updated components in your Cloud Foundry environment
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3801 — 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-3801 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