LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32977: AVEVA System Platform Improper Verification of Cryptographic Signature

AVEVA System Platform versions 2017 through 2020 R2 P01 does not verify, or incorrectly verifies, the cryptographic signature for data.

HighCVSS 7.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

AVEVA System Platform may accept data without properly verifying its cryptographic signature. In an industrial environment, that can undermine trust in system data and could affect confidentiality, integrity, and availability if a highly privileged attacker can reach the system.

Executive priority

Treat this as high priority where AVEVA System Platform supports production operations. The privilege requirement lowers broad internet-scale risk, but compromise of trusted OT administrators or services could create serious operational impact.

Technical view

CVE-2021-32977 is a CWE-347 improper cryptographic signature verification issue in AVEVA System Platform versions 2017 through 2020 R2 P01. CVSS 3.1 is 7.2: network-reachable, low complexity, high privileges required, no user interaction, with high impact across confidentiality, integrity, and availability.

Likely exposure

Likely exposure is limited to organizations running affected AVEVA System Platform versions, especially industrial or operational technology environments where privileged users or services can access the platform over a network.

Exploitation context

The provided bundle does not show CISA KEV listing or active exploitation. The CVSS vector requires high privileges, so this is most concerning after credential compromise, insider misuse, or excessive privileged access within OT networks.

Researcher notes

Evidence supports signature-verification weakness, high CVSS impact, and high privileges required. The prompt bundle does not include exploit details, proof of exploitation, or specific fixed versions, so remediation should be tied to AVEVA and CISA advisory guidance.

Mitigation direction

  • Inventory AVEVA System Platform deployments and confirm exact versions.
  • Check AVEVA and CISA guidance for supported updates or vendor mitigations.
  • Restrict network access to System Platform management and service interfaces.
  • Reduce and monitor high-privilege accounts with access to affected systems.
  • Prioritize remediation in production OT environments with weak segmentation.

Validation and detection

  • Compare installed versions against 2017 through 2020 R2 P01 affected range.
  • Confirm whether vendor-recommended updates or mitigations are applied.
  • Review privileged access paths to affected AVEVA systems.
  • Verify OT network segmentation limits access to required hosts only.
  • Check change records for unexpected configuration or data integrity events.
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-347: 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-32977 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.2 (3.1)
Known Exploited
No
Published

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

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.2CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H1.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
AVEVAAVEVA System Platform2017Listed
Weakness

CWE details

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

CWE-347 · source CWE mapping

Improper Verification of Cryptographic Signature

Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.