CVE-2020-7531
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-284 Improper Access Control vulnerability exists in SCADAPack 7x Remote Connect (V3.6.3.574 and prior) which allows an attacker to place executables in a specific folder and run code whenever RemoteConnect is executed by the user.
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 confidenceThis is an improper access control (CWE-284) vulnerability in SCADAPack 7x Remote Connect where an attacker with write access to a specific folder can place malicious executables that will be automatically executed when a legitimate user launches the RemoteConnect application. This represents a binary/DLL planting attack vector enabling privilege escalation and arbitrary code execution.
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 installed version of SCADAPack Remote ConnectOpen Windows Control Panel, navigate to Programs and Features, or use the 'Add or Remove Programs' list. Locate 'Schneider Electric Scadapack 7x Remote Connect' and note the version number displayed in the Version column.Affected if The displayed version is 3.6.3.574 or any version lower than 3.6.3.574.
-
Locate the Remote Connect installation directoryRight-click the SCADAPack Remote Connect shortcut on the desktop or Start menu, select 'Properties', and examine the 'Target' path to find the installation folder. Common paths include C:\Program Files\Schneider Electric\Scadapack Remote Connect or similar.Affected if The application is installed and the installation folder exists on the system.
-
Identify the vulnerable folder used for automatic executionConsult Schneider Electric security advisory or product documentation for CVE-2020-7531 to identify the specific folder path referenced as susceptible to DLL/executable planting. This is typically a folder within the application directory where the application loads executables automatically on launch.Affected if The specific vulnerable folder exists within the Remote Connect installation directory.
-
Review file system permissions on the vulnerable folderRight-click the identified vulnerable folder, select Properties, then go to the Security tab. Examine the permissions for Users, Authenticated Users, or other relevant groups. Verify which accounts have Write or Modify permissions to this folder.Affected if Untrusted or low-privilege accounts (such as standard Users, or domain users without administrative rights) have Write or Modify permissions to the vulnerable folder.
You are affected if SCADAPack Remote Connect version is 3.6.3.574 or lower AND the vulnerable folder has overly permissive write access allowing untrusted users to place malicious executables.
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 dataRestrict file system permissions on the vulnerable folder to prevent unauthorized write access, and update to a patched version of SCADAPack Remote Connect if available from the vendor.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7531 — 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-7531 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