Code execution via malicious project-file deserialization
Published Jul 21, 2021 · Updated Aug 3, 2024
Deserialization of untrusted data in Schneider Electric SoSafe Configurable before 1.8.1 allows local users to execute code via a malicious project file. The project-file loading path deserializes attacker-controlled data without validating the resulting objects; the affected function and serialization format are undisclosed. Execution requires a user to open the crafted file, after which code runs in the application's security context on the workstation.
Summary
What happened
Deserialization of untrusted data in Schneider Electric SoSafe Configurable before 1.8.1 allows local users to execute code via a malicious project file. The project-file loading path deserializes attacker-controlled data without validating the resulting objects; the affected function and serialization format are undisclosed. Execution requires a user to open the crafted file, after which code runs in the application's security context on the workstation.
The record
- CVE
- CVE-2021-22777
- Published
- Jul 21, 2021
- Updated
- Aug 3, 2024
- Vendor
- Schneider Electric
- Product
- SoSafe Configurable
- Classifications
- CWE-502, CAPEC-586, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 21, 2021CVE 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=SoSafe Configurable prior to V1.8.1
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