CVE-2020-28219
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 · uneditedA CWE-522: Insufficiently Protected Credentials vulnerability exists in EcoStruxure Geo SCADA Expert 2019 (Original release and Monthly Updates to September 2020, from 81.7268.1 to 81.7578.1) and EcoStruxure Geo SCADA Expert 2020 (Original release and Monthly Updates to September 2020, from 83.7551.1 to 83.7578.1), that could cause exposure of credentials to server-side users when web users are logged in to Virtual ViewX.
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 confidenceInsufficiently Protected Credentials vulnerability in EcoStruxure Geo SCADA Expert allows server-side users to view credentials when web users are logged into Virtual ViewX. The flaw exposes sensitive authentication data to privileged users who should not have access.
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>= 81.7268.1, <= 81.7578.1>= 83.7551.1, <= 83.7578.1CVSS 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.1/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 Geo SCADA Expert versionOpen the Geo SCADA Expert client, go to Help > About, or check Windows Programs and Features for the exact version number (for example, 81.x.x.x or 83.x.x.x)Affected if The version falls within 81.7268.1 to 81.7578.1 (2019) or 83.7551.1 to 83.7578.1 (2020)
-
Confirm Virtual ViewX web interface is enabledAccess the Geo SCADA Expert web portal URL (typically port 80/443 on the server) or check the server configuration for Virtual ViewX service statusAffected if Virtual ViewX is accessible and users can log in via the web interface
-
Verify server-side user access to credentialsLog in as a server-side (full) user and navigate to the credentials or authentication configuration area within the ViewX client, then check if sensitive credential data is visible in plain textAffected if Server-side users can view credentials that should be hidden or masked while web users are logged into Virtual ViewX
-
Check for credential exposure in logs or memoryReview Geo SCADA Expert logs or runtime memory dumps for plaintext credential data that should have been protectedAffected if Credential data appears in logs, dumps, or screens in plaintext when it should be redacted
You are affected if your installed version is within the 2019 range 81.7268.1-81.7578.1 or the 2020 range 83.7551.1-83.7578.1 AND Virtual ViewX web access is enabled, allowing server-side users to view normally protected credentials.
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 dataApply the vendor patch or update to a version beyond 81.7578.1 (2019) or 83.7578.1 (2020). If no patch available, restrict server-side access and monitor for unauthorized credential access.
- 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-2020-28219 — 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-28219 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