Controller data tampering via weak IPC access controls
Published Apr 29, 2020 · Updated Aug 4, 2024
Access-control weakness in ABB 800xA for DCI before 6.1.1 allows local users to read or write controller data or crash processes. Same-machine IPC objects use weak access-control settings, allowing a crafted local application to inject garbage or structured data into exchanges between Windows processes. Exploitation requires an authenticated account and code execution on a system node; injected data can corrupt runtime values, drive incorrect controller actions, or interrupt the node.
Summary
What happened
Access-control weakness in ABB 800xA for DCI before 6.1.1 allows local users to read or write controller data or crash processes. Same-machine IPC objects use weak access-control settings, allowing a crafted local application to inject garbage or structured data into exchanges between Windows processes. Exploitation requires an authenticated account and code execution on a system node; injected data can corrupt runtime values, drive incorrect controller actions, or interrupt the node.
The record
- CVE
- CVE-2020-8484
- Published
- Apr 29, 2020
- Updated
- Aug 4, 2024
- Vendor
- ABB
- Product
- ABB 800xA for DCI
- Classifications
- CWE-264, T0814, T0836
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 29, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=all versions
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