dbcve.org
Cloud Foundry Elastic RuntimeApplication · Pivotal Software

CVE-2017-4955

CRITICAL · 9.8 CVSS v3.0 Published 2017-06-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
An issue was discovered in Pivotal PCF Elastic Runtime 1.6.x versions prior to 1.6.65, 1.7.x versions prior to 1.7.48, 1.8.x versions prior to 1.8.28, and 1.9.x versions prior to 1.9.5. Several credentials were present in the logs for the Notifications errand in the PCF Elastic Runtime tile.

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

Sensitive credentials were inadvertently written to log files for the Notifications errand in Pivotal Cloud Foundry (PCF) Elastic Runtime. This is an information disclosure vulnerability where authentication secrets were exposed in plaintext logs, potentially allowing unauthorized access to the affected system components.

MitigationUpdate PCF Elastic Runtime to version 1.6.65+, 1.7.48+, 1.8.28+, or 1.9.5+ as appropriate. Additionally, rotate any credentials that may have been exposed in the logs and review/clear affected log files.

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
Cloud Foundry Elastic RuntimeApplication
Affected:= 1.6.0= 1.6.1= 1.6.2= 1.6.3= 1.6.4= 1.6.5= 1.6.6= 1.6.7= 1.6.8= 1.6.9= 1.6.10= 1.6.11

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 checks

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

  1. Determine Elastic Runtime version
    Use the cf CLI or Ops Manager interface to query the installed version of Elastic Runtime. In Ops Manager, navigate to the Elastic Runtime tile and check the version information.
    Affected if The installed version matches 1.6.0 through 1.6.11 inclusive.
  2. Identify if Notifications errand is deployed
    Check the deployment manifest or query the Cloud Foundry deployment for the presence and status of the Notifications errand component.
    Affected if The Notifications errand is present in the deployment.
  3. Locate Notifications errand log files
    Access the log files generated by the Notifications errand. These are typically stored in the VM where the Notifications errand runs, under paths such as /var/vcap/sys/log/notifications or similar log directories for the Notifications component.
    Affected if Log files exist for the Notifications errand.
  4. Search log files for credential patterns
    Grep or search through the Notifications errand log files for patterns that resemble credentials, API keys, passwords, or tokens in plaintext. Look for strings containing keywords like 'password', 'secret', 'token', 'credential', or base64-encoded strings that may decode to sensitive values.
    Affected if Plaintext credentials, authentication secrets, or API tokens are found in the logs.
  5. Review historical logs for exposure
    Examine archived or rotated log files from the Notifications errand, as credentials may have been written during specific operations. Check log rotation archives if available.
    Affected if Historical log files contain exposed credentials.

You are affected if your Elastic Runtime version is between 1.6.0 and 1.6.11 inclusive AND the Notifications errand is deployed, with plaintext credentials appearing in its log files.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update PCF Elastic Runtime to version 1.6.65+, 1.7.48+, 1.8.28+, or 1.9.5+ as appropriate. Additionally, rotate any credentials that may have been exposed in the logs and review/clear affected log files.

Recommended fix High confidence

Elastic Runtime 1.6.65 or later (or migrate to a supported 1.7.x/1.8.x/1.9.x line with respective patches: 1.7.48+, 1.8.28+, 1.9.5+)

  1. Log in to the Pivotal Cloud Foundry Ops Manager interface
  2. Navigate to the Elastic Runtime tile in the Installation Dashboard
  3. Click on the tile and select 'Upgrade'
  4. Select the appropriate stemcell if prompted
  5. Review and configure any new settings in the tile
  6. Click 'Apply Changes' to deploy the updated version
  7. Verify the upgrade completed successfully by checking the Elastic Runtime status
Caveat Upgrading Elastic Runtime may require stemcell updates and could impact runtime behavior; test in staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cloud Foundry Elastic Runtime Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-4955 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2017-4955 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