CVE-2020-10600
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 authenticated remote attacker could crash PI Archive Subsystem when the subsystem is working under memory pressure. This can result in blocking queries to PI Data Archive (2018 SP2 and prior versions).
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 confidenceAn authenticated remote attacker can crash the PI Archive Subsystem by exploiting a memory pressure condition, causing denial of service by blocking all queries to the PI Data Archive. The vulnerability affects versions 2018 SP2 and prior.
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<= 2019CVSS 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
- None
- Integrity
- Low
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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.
-
Verify PI Data Archive installationCheck for the PI Data Archive service (pisdk or PI Archive Subsystem service) in Windows Services or look for OSIsoft PI installation directories (typically C:\Program Files\OSIsoft\PI).Affected if PI Data Archive service or installation directory is found on the system
-
Determine installed PI Data Archive versionOpen PI System Management Tools (PISMT) or check the PI Archive version through the PI SDK. Alternatively, check the executable version of pias.exe or the PI Archive Subsystem binary.Affected if Unable to determine version or version is 2018 SP2 or prior, or version is listed as 2019 or earlier
-
Confirm PI Archive Subsystem is runningVerify the PI Archive Subsystem service (PI Archive or related service) is in a running state in Windows Services.Affected if Service is running and version falls within affected range (<= 2018 SP2 or <= 2019)
-
Assess network exposureReview firewall rules and network configuration to determine if the PI Data Archive (typically port 5450) is accessible to untrusted networks or external IP addresses.Affected if PI Data Archive ports are exposed to untrusted networks without proper authentication controls
A user is affected if PI Data Archive version 2018 SP2 or prior (or version <= 2019) is installed and the PI Archive Subsystem is running and network-accessible to authenticated attackers.
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 Archive Subsystem to a version newer than 2018 SP2, or apply vendor-supplied patches. Until then, limit network access to authenticated users and monitor for service disruptions.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10600 — 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-2020-10600 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