CVE-2019-3785
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, versions prior to 1.78.0, contain an endpoint with improper authorization. A remote authenticated malicious user with read permissions can request package information and receive a signed bit-service url that grants the user write permissions to the bit-service.
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 Cloud Controller versions prior to 1.78.0 contain an authorization bypass vulnerability where an endpoint returns a signed bit-service URL with write permissions to users who only have read permissions. This allows an authenticated user with read-only access to escalate privileges by obtaining a signed URL that grants write access to the bit-service.
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.78.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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 Capi Release versionCheck the deployed version of the Cloud Foundry Capi Release by querying bosh or the deployment manifest: `bosh deployments | grep -i capi` or inspect the release version file if accessible.Affected if The Capi Release version is below 1.78.0
-
Verify Cloud Controller API versionQuery the Cloud Controller API info endpoint: `curl -s https://api.<system-domain>/v2/info` and check the api_version field, or use `cf curl /v2/info` to retrieve version details.Affected if The underlying Cloud Controller code corresponds to a version prior to 1.78.0
-
Confirm bit-service integration is enabledCheck if the bit-service (package resource) functionality is configured in the Cloud Foundry deployment by reviewing manifest settings for bits-service, packages, or droplet_repository settings.Affected if The bit-service or package upload functionality is enabled and accessible to users
-
Test for authorization bypassUsing a user account with only read-only permissions (read actor role), attempt to access package or buildpack endpoints that return signed URLs: `cf curl /v2/packages/<guid>` or `cf curl /v2/buildpacks/<guid>` and examine if the response contains a signed URL with upload/write permissions.Affected if A read-only user receives a signed URL that includes write or upload permissions in the response
A user is affected if the Capi Release version is below 1.78.0 AND the bit-service functionality is enabled, allowing authenticated read-only users to obtain write-access signed URLs.
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.78.0
Upgrade Cloud Foundry Cloud Controller to version 1.78.0 or later. Additionally, audit affected deployments to verify no unauthorized access occurred and ensure authorization checks are properly enforced on package information endpoints.
- Consultation6.0 h
- Implementation10.0 h
- Testing8.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 $7,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3785 — 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-3785 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