Service interruption via uncaught AutoBuild exception
Published Apr 4, 2022 · Updated Apr 16, 2025
Uncaught exception in AVEVA System Platform 2017 through 2020 R2 P01 allows remote attackers to interrupt the AutoBuild service. An undisclosed AutoBuild function throws an exception while processing crafted network input, and the service fails to catch it. No authentication or user interaction is required; availability is exposed only where the AutoBuild service remains enabled.
Summary
What happened
Uncaught exception in AVEVA System Platform 2017 through 2020 R2 P01 allows remote attackers to interrupt the AutoBuild service. An undisclosed AutoBuild function throws an exception while processing crafted network input, and the service fails to catch it. No authentication or user interaction is required; availability is exposed only where the AutoBuild service remains enabled.
The record
- CVE
- CVE-2021-33010
- Published
- Apr 4, 2022
- Updated
- Apr 16, 2025
- Vendor
- AVEVA
- Product
- AVEVA System Platform
- Classifications
- CWE-248, T1499
- Attack vector
- network
- Privileges
- unauthenticated
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.
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