CVE-2017-7934
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 Improper Authentication issue was discovered in OSIsoft PI Server 2017 PI Data Archive versions prior to 2017. PI Network Manager using older protocol versions contains a flaw that could allow a malicious user to authenticate with a server and then cause PI Network Manager to behave in an undefined manner.
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 confidenceImproper authentication vulnerability in OSIsoft PI Server 2017 PI Data Archive's PI Network Manager when using older protocol versions. A malicious user can authenticate to the server but causes PI Network Manager to behave in an undefined manner due to flaws in how older protocol versions handle the authentication flow.
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<= 3.4.410.1256CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/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 PI Data Archive versionCheck the installed version of PI Data Archive (PI DA) on the server. This can typically be found in Windows Add/Remove Programs, or by examining the PI Data Archive service information.Affected if The installed version is 3.4.410.1256 or lower.
-
Determine if older protocol versions are in useReview PI Network Manager configuration and logs to identify if any clients or connections are using older protocol versions (pre-2017 protocols). Check PI Network Manager settings for protocol version handling.Affected if Older protocol versions (version 3.x or earlier protocols) are enabled or active in the environment.
-
Inspect PI Network Manager authentication behaviorExamine PI Network Manager logs for anomalies during authentication attempts using older protocol versions. Look for undefined or unexpected behavior in authentication flows.Affected if Authentication attempts via older protocols cause unexpected behavior in PI Network Manager.
-
Verify PI Server product family versionConfirm the full PI Server 2017 version string. The vulnerability specifically affects PI Data Archive components <= 3.4.410.1256 within the PI Server 2017 product line.Affected if The PI Data Archive component version is at or below 3.4.410.1256.
A user is affected if their PI Data Archive version is 3.4.410.1256 or lower AND older protocol versions are enabled or in use, allowing malformed authentication flows to trigger undefined behavior in PI Network Manager.
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 dataUpgrade PI Data Archive to version 2017 or later to eliminate older vulnerable protocol versions. Verify no older protocol clients remain in the environment.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-7934 — 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-7934 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