LiveActive security incident?Get immediate response
CVE Record

CVE-2021-27505: mySCADA myPRO Exposure of Information Through Directory Listing

mySCADA myPRO versions prior to 8.20.0 does not restrict unauthorized read access to sensitive directory listing information.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

mySCADA myPRO before 8.20.0 could let unauthenticated network users view sensitive directory listings. This is primarily a confidentiality issue: exposed file names or contents may reveal operational, configuration, or system information useful to attackers. Because myPRO is SCADA software, prioritize internet-facing or remotely accessible deployments.

Executive priority

Treat this as a near-term remediation item for any SCADA environment using myPRO. It does not indicate system takeover by itself, but sensitive operational disclosure can support later attacks. Prioritize externally reachable systems first.

Technical view

CVE-2021-27505 is CWE-548 in mySCADA myPRO before 8.20.0. The CVSS 3.1 vector indicates network access, low complexity, no privileges, no user interaction, and high confidentiality impact, with no stated integrity or availability impact.

Likely exposure

Organizations running mySCADA myPRO versions prior to 8.20.0 are potentially exposed, especially if the web interface is reachable from untrusted networks. The source bundle does not provide exact affected subversions, CPEs, or deployment prerequisites beyond versions before 8.20.0.

Exploitation context

The provided data does not show CISA KEV listing or active exploitation evidence. The vulnerability is remotely reachable and unauthenticated per CVSS, so exposed instances should be treated as high-priority information disclosure risk even without confirmed exploitation.

Researcher notes

The public bundle identifies the weakness class, affected product, fixed version threshold, and CVSS vector, but not exact vulnerable directories, affected subversions, or exploit observations. Avoid assuming broader mySCADA products are affected without vendor confirmation.

Mitigation direction

  • Upgrade mySCADA myPRO to version 8.20.0 or later.
  • Review CISA and mySCADA guidance for any deployment-specific instructions.
  • Restrict myPRO access to trusted networks and authenticated administrative paths.
  • Remove direct internet exposure where operationally feasible.
  • Monitor vendor advisories for any later affected-version clarification.

Validation and detection

  • Inventory all mySCADA myPRO deployments and record exact versions.
  • Confirm no production instance runs a version earlier than 8.20.0.
  • Check whether myPRO interfaces are reachable from untrusted networks.
  • Verify directory listings are not exposed to unauthenticated users.
  • Review access logs for unusual unauthenticated file enumeration patterns.
Prepared
Confidence
medium
Sources
4

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-548: 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
cve · low confidence lookup

CVE-2021-27505 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
3Source 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-27505Attack 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
mySCADAmyPROunspecifiedListed
Weakness

CWE details

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

CWE-548 · source CWE mapping

Exposure of Information Through Directory Listing

Exposure of Information Through Directory Listing represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.