CVE-2019-11277
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 NFS Volume Service, 1.7.x versions prior to 1.7.11 and 2.x versions prior to 2.3.0, is vulnerable to LDAP injection. A remote authenticated malicious space developer can potentially inject LDAP filters via service instance creation, facilitating the malicious space developer to deny service or perform a dictionary attack.
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 NFS Volume Service versions 1.7.x prior to 1.7.11 and 2.x prior to 2.3.0 are vulnerable to LDAP injection. An authenticated malicious space developer can inject arbitrary LDAP filters through service instance creation parameters, potentially causing denial of service or enabling dictionary attacks against the LDAP directory.
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< 11.1.0>= 1.7.0, < 1.7.11>= 2.0.0, < 2.3.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
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 NFS Volume Release versionQuery the BOSH deployment for the nfs-volume-release: run `bosh deployments` and look for nfs-volume or nfsv3-volume, then run `bosh deployment <deployment-name>` to see the release version, or check the stemcell and release versions in the deployment manifest.Affected if The NFS Volume Release version is 1.7.0 through 1.7.10, or 2.0.0 through 2.2.x.
-
Identify Cloud Foundry Deployment versionRun `cf target` to confirm your API endpoint, then check the CF Deployment version via BOSH or the ops manager UI if applicable. The version is typically found in the cf-deployment manifest or by querying `bosh deployments | grep cf-`Affected if The CF Deployment version is below 11.1.0.
-
Confirm LDAP integration is configuredExamine the NFS Volume Service broker configuration: check the deployment manifest for LDAP-related settings such as `ldap_url`, `ldap_user_dn`, `ldap_password`, or `ldap_search_base`. These are typically found in the nfs-broker or nfs-volume-job properties.Affected if LDAP is configured as the authentication or lookup backend for the NFS Volume Service.
-
Review service instance creation logsRun `cf serviceinstances` to list instances, then review the NFS Volume Service broker logs via `bosh logs nfs-broker --recent` or the relevant job logs. Look for LDAP filter construction in the logs during service instance provisioning.Affected if Service instances were created using custom parameters, and LDAP filters appear to be constructed from unsanitized user input in the logs.
Your environment is affected if the NFS Volume Release is below 1.7.11 or below 2.3.0 (or CF Deployment is below 11.1.0) AND LDAP integration is enabled, allowing an authenticated space developer to inject arbitrary LDAP filters through service instance parameters.
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.7.112.3.011.1.0
Upgrade the NFS Volume Service to version 1.7.11 or later, or 2.3.0 or later. Implement proper input validation and escaping of user-supplied parameters before using them in LDAP filter construction.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11277 — 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-11277 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