What is the severity of CVE-2021-33013?

CVE-2021-33013 is classified as a medium severity vulnerability due to the potential unauthorized access to sensitive system information.

How do I fix CVE-2021-33013?

The recommended fix for CVE-2021-33013 is to upgrade mySCADA myPRO to version 8.20.0 or later.

What types of information are vulnerable in CVE-2021-33013?

CVE-2021-33013 allows unauthorized read access to sensitive system information, which can include configuration and operational data.

Which versions of mySCADA are affected by CVE-2021-33013?

CVE-2021-33013 affects all versions of mySCADA and myPRO prior to 8.20.0.

Is there a workaround for CVE-2021-33013?

Currently, the only effective solution for CVE-2021-33013 is to upgrade to the latest version, as there are no known workarounds listed.

Vulnerability/
CVE-2021-33013

high

8.2

CWE

862 284

13/5/2022

16/9/2024

CVE-2021-33013: mySCADA myPRO Improper Access Control

First published: Fri May 13 2022(Updated: )

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

Credit: ics-cert@hq.dhs.gov

Affected Software	Affected Version	How to fix
mySCADA All versions prior to 8.20.0
mySCADA myPRO Manager	<8.20.0

Remedy

mySCADA recommends users apply update v8.20.0 or later.

Never miss a vulnerability like this again

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

ICSA-21-217-03

Frequently Asked Questions

What is the severity of CVE-2021-33013?
CVE-2021-33013 is classified as a medium severity vulnerability due to the potential unauthorized access to sensitive system information.
How do I fix CVE-2021-33013?
The recommended fix for CVE-2021-33013 is to upgrade mySCADA myPRO to version 8.20.0 or later.
What types of information are vulnerable in CVE-2021-33013?
CVE-2021-33013 allows unauthorized read access to sensitive system information, which can include configuration and operational data.
Which versions of mySCADA are affected by CVE-2021-33013?
CVE-2021-33013 affects all versions of mySCADA and myPRO prior to 8.20.0.
Is there a workaround for CVE-2021-33013?
Currently, the only effective solution for CVE-2021-33013 is to upgrade to the latest version, as there are no known workarounds listed.

agent/weakness
agent/type
agent/references
agent/author
agent/description
collector/ics-cert-advisory
source/ICS
agent/software-canonical-lookup
agent/software-canonical-lookup-request
agent/softwarecombine
agent/severity
agent/title
collector/mitre-cve
source/MITRE
agent/remedy
agent/last-modified-date
agent/first-publish-date
agent/event
agent/trending
agent/source
agent/tags
collector/nvd-index
vendor/myscada
canonical/myscada all versions prior to 8.20.0
canonical/myscada mypro manager

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2021-33013?
CVE-2021-33013 is classified as a medium severity vulnerability due to the potential unauthorized access to sensitive system information.
How do I fix CVE-2021-33013?
The recommended fix for CVE-2021-33013 is to upgrade mySCADA myPRO to version 8.20.0 or later.
What types of information are vulnerable in CVE-2021-33013?
CVE-2021-33013 allows unauthorized read access to sensitive system information, which can include configuration and operational data.
Which versions of mySCADA are affected by CVE-2021-33013?
CVE-2021-33013 affects all versions of mySCADA and myPRO prior to 8.20.0.
Is there a workaround for CVE-2021-33013?
Currently, the only effective solution for CVE-2021-33013 is to upgrade to the latest version, as there are no known workarounds listed.