dbcve.org
System PlatformApplication · Aveva

CVE-2021-32977

HIGH · 7.2 CVSS v3.1 Published 2022-04-04
Fix available
A fix is available. Upgrade to 2020 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
AVEVA System Platform versions 2017 through 2020 R2 P01 does not verify, or incorrectly verifies, the cryptographic signature for data.

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

AVEVA System Platform versions 2017 through 2020 R2 P01 fails to properly verify cryptographic signatures on data, allowing potentially tampered or malicious data to be accepted by the system due to missing or incorrect signature validation.

MitigationUpgrade to a patched version of AVEVA System Platform beyond 2020 R2 P01. Until then, implement additional integrity checks on data imports and restrict network access to reduce attack surface.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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. Identify installed AVEVA System Platform version
    Locate the installation directory or check Windows Programs and Features for 'AVEVA System Platform' and note the exact version number (such as 2017, 2017 R2, 2019, 2020, or 2020 R2)
    Affected if The installed version is 2017, 2018, 2019, or 2020 (any release) since these all lack proper cryptographic signature validation
  2. Determine if data import or external data feeding is configured
    Review system configuration for any data import features, OPC connections, external data sources, or data exchange modules that bring external data into the AVEVA environment
    Affected if The system imports or accepts data from external sources without additional integrity controls
  3. Check for disabled or missing signature validation settings
    Examine the security or data handling configuration files and settings within AVEVA System Platform related to cryptographic verification, digital signatures, or data integrity checks
    Affected if Signature validation is disabled, not configured, or missing from the data handling settings
  4. Inspect network exposure of data ingestion interfaces
    Review network configuration to identify if the system's data import interfaces (such as OPC servers, data exchange ports, or import utilities) are exposed to untrusted network segments
    Affected if Data ingestion interfaces are accessible on open or untrusted networks without additional integrity validation

A user is affected if they have AVEVA System Platform version 2017 through 2020 installed and the system is configured to accept external data imports without supplementary integrity verification.

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

Upgrade to a patched version of AVEVA System Platform beyond 2020 R2 P01. Until then, implement additional integrity checks on data imports and restrict network access to reduce attack surface.

Recommended fix Moderate confidence

2020 R2 P02 or later (contact AVEVA for specific fixed release)

  1. Verify current AVEVA System Platform version by checking the installed version in Control Studio or through the Windows Programs and Features list
  2. Contact AVEVA customer support to obtain the appropriate patch or upgrade to a fixed release
  3. Plan upgrade during a scheduled maintenance window to minimize operational impact
  4. Before upgrading, back up all current configurations, projects, and historical data
  5. Apply the upgrade following AVEVA's official installation documentation
  6. After upgrade, verify that all signature verification mechanisms are functioning correctly
  7. Validate that all existing projects and integrations operate as expected in the updated version
Caveat Review AVEVA upgrade documentation for any configuration or compatibility changes between 2020 R2 P01 and the target version

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
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-32977 — 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-32977 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