CVE-2017-14390
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 · uneditedIn Cloud Foundry Foundation cf-deployment v0.35.0, a misconfiguration with Loggregator and syslog-drain causes logs to be drained to unintended locations.
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 confidenceIn Cloud Foundry Foundation cf-deployment v0.35.0, a misconfiguration in the Loggregator component's syslog-drain settings causes application logs to be routed to unintended destinations instead of the configured syslog endpoints. This exposes potentially sensitive application data by leaking logs to incorrect locations.
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= 0.35.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
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 cf-deployment versionQuery your Cloud Foundry deployment management system or check the cf-deployment manifest file for the version identifierAffected if The installed version is exactly 0.35.0
-
Locate Loggregator syslog-drain configurationFind the Loggregator component configuration in your cf-deployment manifest or BOSH deployment configurationAffected if Loggregator syslog-drain settings are present in the deployment configuration
-
Inspect configured drain endpointsReview the syslog_drain configuration section to identify all configured drain URLs and their destinationsAffected if Multiple drain URLs are configured or URLs point to unexpected/incorrect destinations
-
Verify drain credentials and scopingExamine the credentials associated with each syslog drain endpoint and check whether they are properly scoped to authorized destinations onlyAffected if Credentials are overly permissive or drains lack proper access controls
-
Compare expected vs actual log routingCorrelate the intended syslog endpoints from your network architecture with the actual destinations found in the drain configurationAffected if Actual drain destinations do not match the intended/configured syslog endpoints
You are affected if running cf-deployment version 0.35.0 with Loggregator syslog-drain configured and the drain destinations differ from your intended syslog endpoints.
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 dataReview and correct the Loggregator syslog-drain configuration in cf-deployment to ensure logs are routed only to the intended syslog endpoints; verify the drain URLs and credentials are properly scoped.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14390 — 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-2017-14390 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