Cf DeploymentApplication · Cloudfoundry

CVE-2019-11283

HIGH · 8.8 CVSS v3.1 Published 2019-10-23
Fix available
A fix is available. Upgrade to 2.0.3 / 12.2.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Cloud Foundry SMB Volume, versions prior to v2.0.3, accidentally outputs sensitive information to the logs. A remote user with access to the SMB Volume logs can discover the username and password for volumes that have been recently created, allowing the user to take control of the SMB Volume.

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 confidence

The Cloud Foundry SMB Volume service (versions prior to v2.0.3) has a sensitive information disclosure vulnerability where username and password credentials for newly created SMB volumes are inadvertently written to service logs. An attacker with access to these logs can retrieve the credentials and gain unauthorized control over the affected SMB volumes.

MitigationUpgrade Cloud Foundry SMB Volume to version v2.0.3 or later to eliminate the credential logging. Additionally, rotate any SMB volume credentials that may have been exposed in logs prior to the upgrade, and review log access controls to limit exposure.

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
Cf DeploymentApplication
Affected:< 12.2.0
Cloud Foundry Smb VolumeApplication
Affected:< 2.0.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if SMB Volume service is deployed
    Query your Cloud Foundry deployment for the SMB Volume service broker. Run 'cf service-brokers' or check the deployment manifests for smb-volume releases.
    Affected if SMB Volume service broker is present in the deployment
  2. Check SMB Volume service version
    Examine the version of the Cloud Foundry SMB Volume release in your deployment. For BOSH deployments, run 'bosh releases' and look for the smb-volume release. Compare the version number against the affected ranges: Cf Deployment < 12.2.0 or Smb Volume < 2.0.3.
    Affected if The installed version is prior to v2.0.3 for SMB Volume or prior to 12.2.0 for Cf Deployment
  3. Determine if any SMB volumes were created
    List all service instances of type SMB in your Cloud Foundry environment using 'cf services' or query the service broker database. Check for any active or deleted SMB volume service instances.
    Affected if Any SMB volume service instances were ever created in the environment
  4. Search service logs for exposed credentials
    Review logs from the SMB Volume service broker and related components (typically found in the syslog or loggregator output). Search for patterns containing 'smb', 'username', 'password', 'credential', 'smbvol' along with what appear to be authentication strings. Focus on timestamps corresponding to SMB volume creation events.
    Affected if Logs contain plaintext SMB username or password strings alongside volume creation events

You are affected if the SMB Volume service is deployed with a version prior to v2.0.3 (or Cf Deployment prior to 12.2.0) AND any SMB volumes were ever created, with credentials visible in service logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 2.0.3 / 12.2.0 or later
Fixed in 2.0.312.2.0
Interim mitigation

Upgrade Cloud Foundry SMB Volume to version v2.0.3 or later to eliminate the credential logging. Additionally, rotate any SMB volume credentials that may have been exposed in logs prior to the upgrade, and review log access controls to limit exposure.

Fix this in Cf Deployment Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11283 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-11283 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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