dbcve.org
System PlatformApplication · Aveva

CVE-2021-33010

HIGH · 7.5 CVSS v3.1 Published 2022-04-04
Fix available
A fix is available. Upgrade to 2020 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An exception is thrown from a function in AVEVA System Platform versions 2017 through 2020 R2 P01, but it is not caught, which may cause a denial-of-service condition.

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 confidence

An unhandled exception in AVEVA System Platform versions 2017 through 2020 R2 P01 is thrown from a function but not caught, leading to denial of service. The vulnerability has a CVSS score of 7.5 (HIGH).

MitigationApply vendor-supplied patches or update to a patched version of AVEVA System Platform beyond 2020 R2 P01.

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
System PlatformApplication
Affected:>= 2017, < 2020= 2020

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify AVEVA System Platform installation
    Open Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or check Programs and Features in Control Panel for an entry named 'AVEVA System Platform'
    Affected if No AVEVA System Platform entry is found in installed programs or registry
  2. Locate AVEVA System Platform version
    Check the Windows Registry key HKEY_LOCAL_MACHINE\SOFTWARE\AVEVA\System Platform\ or look for version information in the application's installation directory under a file like version.txt or in the product's About dialog
    Affected if Unable to locate any version information for AVEVA System Platform
  3. Compare installed version to affected range
    Review the identified version number. The affected versions are: 2017, 2018, 2019, and 2020 (all builds). Version 2020 R2 P01 and later are NOT affected.
    Affected if The installed version is 2017, 2018, 2019, or 2020 (any build) - these versions are within the affected range
  4. Confirm application runs vulnerable code path
    Verify the application is configured to run and exposes network services. This CVE triggers via an unhandled exception in a specific function - monitor application logs for unexpected crashes or exceptions in theAVEVA-related event logs
    Affected if The application runs and experiences unhandled exceptions that cause denial of service conditions

The environment is affected if AVEVA System Platform is installed and the version is 2017, 2018, 2019, or any 2020 release (prior to 2020 R2 P01).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 2020 or later
Fixed in 2020
Interim mitigation

Apply vendor-supplied patches or update to a patched version of AVEVA System Platform beyond 2020 R2 P01.

Recommended fix Moderate confidence

AVEVA System Platform 2020 R2 P02 or later (contact AVEVA for latest supported release)

  1. Verify current AVEVA System Platform version through the system's about or version information panel
  2. Review the official AVEVA security advisory at www.aveva.com for the complete list of affected versions
  3. Review CISA advisory ICSA-21-287-02 at www.cisa.gov for additional technical details
  4. Plan maintenance window for the upgrade procedure
  5. Back up current system configuration and any custom scripts
  6. Upgrade to AVEVA System Platform 2020 R2 P02 or later (the first fixed release after the vulnerable versions)
  7. Verify the upgrade was successful by checking the version information
  8. Test critical operations to confirm normal system functionality
Caveat Review AVEVA compatibility documentation for your specific integrations; upgrading major versions may require testing of custom scripts and third-party connectors

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in System Platform Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-33010 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-33010 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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