CVE-2017-5153
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 · uneditedAn issue was discovered in OSIsoft PI Coresight 2016 R2 and earlier versions, and PI Web API 2016 R2 when deployed using the PI AF Services 2016 R2 integrated install kit. An information exposure through server log files vulnerability has been identified, which may allow service account passwords to become exposed for the affected services, potentially leading to unauthorized shutdown of the affected PI services as well as potential reuse of domain credentials.
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 confidenceOSIsoft PI Coresight 2016 R2 and earlier and PI Web API 2016 R2 (when deployed via PI AF Services 2016 R2 integrated install kit) expose service account passwords in plaintext within server log files. This information disclosure allows attackers with log access to obtain credentials for the affected services.
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<= 2016-r2= 2016-r2CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed PI Coresight versionOpen Windows Programs and Features (appwiz.cpl) or check registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for OSIsoft PI Coresight entry and note the Version stringAffected if Version is 2016 R2 or earlier (e.g., versions like 1.10.x, 1.11.x, 1.12.x corresponding to 2016, 2016 R2)
-
Identify installed PI Web API versionOpen Windows Programs and Features or check registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for OSIsoft PI Web API entry and note the Version stringAffected if Version is exactly 2016 R2
-
Locate PI Coresight log filesNavigate to the logs directory within the PI Coresight installation folder (commonly C:\Program Files\OSIsoft\PI\Coresight\Logs or C:\Program Files\OSIsoft\Coresight\Logs) and list all .log files presentAffected if Log files exist in the expected installation logs folder
-
Search log files for plaintext passwordsOpen each log file and search for strings containing keywords such as 'password', 'pwd', 'pass=', 'user=', or look for patterns where credentials appear in plaintext after login/authentication events. Use findstr /s or a text editor with search capability.Affected if Any log file contains plaintext password strings or credential values in clear text format
You are affected if you have PI Coresight 2016 R2 or earlier OR PI Web API 2016 R2 installed AND their log files contain plaintext service account passwords.
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 dataImmediately rotate all exposed service account passwords, audit and securely delete/secure the affected log files, and reconfigure logging to prevent sensitive credential data from being written to logs. Upgrade to patched versions where available.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5153 — 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-5153 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