CVE-2017-6021
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 · uneditedIn Schneider Electric ClearSCADA 2014 R1 (build 75.5210) and prior, 2014 R1.1 (build 75.5387) and prior, 2015 R1 (build 76.5648) and prior, and 2015 R2 (build 77.5882) and prior, an attacker with network access to the ClearSCADA server can send specially crafted sequences of commands and data packets to the ClearSCADA server that can cause the ClearSCADA server process and ClearSCADA communications driver processes to terminate. A CVSS v3 base score of 7.5 has been assigned; the CVSS vector string is (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H).
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 denial of service vulnerability exists in Schneider Electric ClearSCADA versions 2014 R1 through 2015 R2. An unauthenticated remote attacker with network access can send specially crafted sequences of commands and data packets to the ClearSCADA server, causing both the ClearSCADA server process and ClearSCADA communications driver processes to terminate unexpectedly.
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<= 2010= 2014= 2015CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 ClearSCADA installation and versionLocate the ClearSCADA installation directory or check Windows registry for installed software version information. Common paths may include Program Files/Schneider Electric/ClearSCADA or Program Files/Aveva/ClearSCADA.Affected if The installed version matches 2014 R1, 2014 R2, 2015 R1, 2015 R2, or falls within the 2014 through 2015 range.
-
Confirm exact version numberRetrieve the detailed version number from the ClearSCADA server executable or about dialog if accessible. Compare against the affected range: versions 2014 R1 through 2015 R2.Affected if The exact version is 2014 R1, 2014 R2, 2015 R1, 2015 R2, or any 2014.x/2015.x variant.
-
Assess network accessibility of ClearSCADA serverDetermine if the ClearSCADA server TCP ports (typically 5480, 5481, or configured service ports) are exposed to untrusted networks or the internet. Use network scanning or review firewall rules.Affected if The ClearSCADA server ports are accessible from unauthenticated external networks without proper firewall restrictions.
-
Verify server and driver processes are runningCheck Windows Task Manager or use command-line tools to confirm ClearSCADA server process and communications driver processes are currently active.Affected if Either the ClearSCADA server process or communications driver processes are not running, which may indicate the vulnerability has been exploited.
If ClearSCADA version 2014 R1 through 2015 R2 is installed and its server ports are network-accessible, the environment is affected by this CVE.
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 available vendor patches or updates to ClearSCADA. Until patches are applied, restrict network access to the ClearSCADA server using firewalls or network segmentation to prevent unauthorized external attackers from reaching the service.
- Consultation8.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,008.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6021 — 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-2017-6021 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