CVE-2020-7528
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-502 Deserialization of Untrusted Data vulnerability exists in SCADAPack 7x Remote Connect (V3.6.3.574 and prior) which could allow arbitrary code execution when an attacker builds a custom .PRJ file containing a malicious serialized buffer.
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 confidenceA CWE-502 deserialization vulnerability exists in SCADAPack 7x Remote Connect (V3.6.3.574 and prior) where the application deserializes data from .PRJ project files without proper validation. An attacker can craft a malicious .PRJ file containing a crafted serialized buffer that, when processed by the application, leads to arbitrary code execution on the target system.
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.6.3.574CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 if SCADAPack 7x Remote Connect is installedOn Windows, check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for an entry named 'SCADAPack 7x Remote Connect' or look in C:\Program Files\Schneider Electric\SCADAPack 7x Remote Connect for the application directoryAffected if The application is found installed on the system
-
Determine the installed version of the softwareRight-click on the application executable (typically named RemoteConnect.exe or similar in the install directory) and select Properties, then check the Details tab for the Product Version. Alternatively, check the 'DisplayVersion' value in the registry uninstall key found in the previous stepAffected if The version displayed is 3.6.3.574 or any version lower (e.g., 3.6.3.500, 3.6.2.x, etc.)
-
Verify .PRJ file handling is in useLook for .PRJ project files in common project directories associated with the application (typically found in Documents\Schneider Electric\SCADAPack or within the application installation directory under Projects)Affected if The application is being used to create, open, or process .PRJ project files, which is the normal operation mode of the software
A system is affected by CVE-2020-7528 if SCADAPack 7x Remote Connect version 3.6.3.574 or lower is installed and the application is used to process .PRJ project files, as the vulnerability lies in the deserialization of data within these files.
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 to a patched version of SCADAPack 7x Remote Connect if available from the vendor; otherwise, implement file validation/sanitization for .PRJ files, restrict file imports to trusted sources only, and apply network segmentation to limit exposure of affected systems.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7528 — 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-7528 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