CVE-2020-7532
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 x70 Security Administrator (V1.2.0 and prior) which could allow arbitrary code execution when an attacker builds a custom .SDB 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 in SCADAPack x70 Security Administrator (v1.2.0 and prior) allows attackers to execute arbitrary code by crafting malicious .SDB files containing specially constructed serialized buffers that get processed without proper validation.
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<= 1.2.0CVSS 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.
-
Verify SCADAPack x70 Security Administrator is installedCheck the system for the presence of SCADAPack x70 Security Administrator software - look in Program Files, Program Files (x86), or the application's default installation directory for executables or folders named 'Security Administrator' or containing 'Scadapack'Affected if The application is found installed on the system
-
Determine the installed versionRight-click the Security Administrator executable (typically named something like SecurityAdministrator.exe or similar) and select Properties, then check the Details tab for the File Version or Product Version. Alternatively, check any 'About' or 'Version' menu item within the application itselfAffected if The installed version is 1.2.0 or any version prior to 1.2.0
-
Check for .SDB file handling capabilityLaunch the Security Administrator application and examine whether it has functionality to import, open, or process .SDB files - look for File > Open, Import, or similar menu options that accept .SDB file extensionsAffected if The application can import or process .SDB files and the version is <= 1.2.0
-
Identify user access to the applicationReview which user accounts have access to execute the Security Administrator software and access its .SDB file processing features - check file permissions and user group memberships on the application directory and executableAffected if Untrusted or unauthorized users have access to run the Security Administrator and process .SDB files on an affected version
A user is affected if SCADAPack x70 Security Administrator version 1.2.0 or prior is installed and the application can process .SDB files, allowing deserialization of untrusted serialized data.
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 x70 Security Administrator beyond v1.2.0; if no patch available, implement file validation/monitoring for .SDB files and restrict access to the Security Administrator to trusted personnel only.
- Consultation3.0 h
- Implementation2.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7532 — 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-7532 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