CVE-2021-22657
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 · uneditedmySCADA myPRO: Versions 8.20.0 and prior has a feature where the API password can be specified, which may allow an attacker to inject arbitrary operating system commands through a specific parameter.
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 confidencemySCADA myPRO versions 8.20.0 and prior contains a command injection vulnerability in its API where a specific parameter used for specifying the password allows attackers to inject arbitrary operating system commands. This is a critical flaw with CVSS 9.8, indicating ease of exploitation and complete system compromise potential.
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<= 8.20.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 if mySCADA myPRO is installedCheck your system for the mySCADA myPRO application by searching for its installation directory, service, or executable. Common locations include C:\Program Files\mySCADA or /opt/myscada on Linux systems.Affected if mySCADA myPRO software is found on the system
-
Determine the installed versionLocate the version information for mySCADA myPRO. This is typically found in the application itself (About section), installation logs, or version file within the installation directory. Compare your version against the affected range of <= 8.20.0.Affected if The installed version is 8.20.0 or any earlier version
-
Verify the API component is enabledCheck if the mySCADA API interface is enabled and running. This is typically configured in the mySCADA administration panel, configuration files, or service settings. Look for API-related services or web server configurations.Affected if The mySCADA API service is enabled and accessible
-
Assess network exposure of the APIReview network configuration to determine if the mySCADA API port is exposed to untrusted networks. Check firewall rules, router configurations, and any port forwarding settings that might allow external access to the API endpoints.Affected if The API is reachable from untrusted or external network locations
You are affected if mySCADA myPRO version 8.20.0 or lower is installed with the API interface enabled and exposed, particularly if the password-related parameter is accessible without proper network restrictions.
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 mySCADA myPRO beyond 8.20.0. If patching is not immediately possible, restrict network access to the mySCADA API interface through firewall rules or network segmentation to limit exposure to trusted users only.
- Consultation4.0 h
- Implementation10.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22657 — 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-2021-22657 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