AutoBuild data tampering via unverified signatures
Published Apr 4, 2022 · Updated Apr 16, 2025
Improper signature verification in AVEVA System Platform 2017 through 2020 R2 P01 allows remote authenticated users to alter AutoBuild data. The AutoBuild component accepts data whose cryptographic signature is absent or incorrectly validated; AVEVA has not disclosed the exact data format or verification routine. High-privilege access and an enabled AutoBuild service are required; AVEVA states that chaining the AutoBuild flaws enables system-privilege code execution or denial of service.
Summary
What happened
Improper signature verification in AVEVA System Platform 2017 through 2020 R2 P01 allows remote authenticated users to alter AutoBuild data. The AutoBuild component accepts data whose cryptographic signature is absent or incorrectly validated; AVEVA has not disclosed the exact data format or verification routine. High-privilege access and an enabled AutoBuild service are required; AVEVA states that chaining the AutoBuild flaws enables system-privilege code execution or denial of service.
The record
- CVE
- CVE-2021-32977
- Published
- Apr 4, 2022
- Updated
- Apr 16, 2025
- Vendor
- AVEVA
- Product
- AVEVA System Platform
- Classifications
- CWE-347
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Apr 4, 2022CVE publishedPublication date reported by the CVE source.
- Apr 16, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2017 <=2020 R2 P01
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo