Code execution via unchecked project deserialization
Published Jul 19, 2022 · Updated Aug 3, 2024
Deserialization in SICK Safety Designer 1.11.0 and earlier allows attackers to execute code by inducing a user to open a project file. A .NET framework class processes serialized project-file content without properly checking it, allowing attacker-controlled objects to execute during opening or import. A user must manually open or import the malicious file, and the resulting code runs with that user's privileges, enabling data access, modification, or application interruption.
Summary
What happened
Deserialization in SICK Safety Designer 1.11.0 and earlier allows attackers to execute code by inducing a user to open a project file. A .NET framework class processes serialized project-file content without properly checking it, allowing attacker-controlled objects to execute during opening or import. A user must manually open or import the malicious file, and the resulting code runs with that user's privileges, enabling data access, modification, or application interruption.
The record
- CVE
- CVE-2022-27580
- Published
- Jul 19, 2022
- Updated
- Aug 3, 2024
- Vendor
- SICK AG
- Product
- SICK Safety Designer
- Classifications
- CWE-502, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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 up to and including 1.11.0
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