LiveActive security incident?Get immediate response
CVE Record

CVE-2021-43989: mySCADA myPRO

mySCADA myPRO Versions 8.20.0 and prior stores passwords using MD5, which may allow an attacker to crack the previously retrieved password hashes.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

mySCADA myPRO 8.20.0 and earlier used MD5 to store passwords. If an attacker has obtained the stored password hashes, MD5 makes offline cracking more practical, potentially exposing user credentials.

Executive priority

Treat as high priority for operational technology environments using mySCADA myPRO. Focus first on exposure inventory, vendor guidance, and credential rotation where hash access is plausible.

Technical view

The issue is CWE-916: insufficient computational effort in password hashing. CVSS 3.1 score is 7.5 high, with high confidentiality impact. The source description ties practical impact to previously retrieved password hashes.

Likely exposure

Organizations running mySCADA myPRO 8.20.0 or earlier are the likely exposure group, especially where attackers could access backups, databases, exports, or other stored credential material.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Exploitation risk depends on attackers first obtaining password hashes, then cracking them offline.

Researcher notes

Evidence is limited to the CVE description and CISA reference. Do not assume a public exploit, active exploitation, or a specific patch unless confirmed in vendor or CISA guidance.

Mitigation direction

  • Inventory mySCADA myPRO deployments and identify versions 8.20.0 or earlier.
  • Review CISA and vendor guidance for fixed versions or compensating controls.
  • Restrict access to myPRO management interfaces and credential storage locations.
  • Rotate affected credentials if password hashes may have been retrieved.
  • Monitor logs for suspicious access to user or credential data.

Validation and detection

  • Confirm installed mySCADA myPRO versions against the affected 8.20.0-and-prior range.
  • Review whether password hashes were exposed through backups, databases, exports, or logs.
  • Check for unexpected access to credential stores or administrative interfaces.
  • Verify remediation guidance directly with mySCADA or the CISA advisory.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-916: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-43989 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-43989Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
mySCADAmyPROAllListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-916 · source CWE mapping

Use of Password Hash With Insufficient Computational Effort

Use of Password Hash With Insufficient Computational Effort represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.