SYSTEM code execution via malicious user deserialization
Published Mar 28, 2022 · Updated Aug 4, 2024
Untrusted deserialization in Schneider Electric SESU SUT Service 2.1.1 through 2.3.0 allows local users to execute code as SYSTEM. Schneider Electric identifies deserialization of a malicious user during authentication but has not disclosed the file, function, format, or unsafe API. Exploitation requires local access and user interaction and grants the resulting code the service's SYSTEM privileges, enabling full compromise of the Windows host.
Summary
What happened
Untrusted deserialization in Schneider Electric SESU SUT Service 2.1.1 through 2.3.0 allows local users to execute code as SYSTEM. Schneider Electric identifies deserialization of a malicious user during authentication but has not disclosed the file, function, format, or unsafe API. Exploitation requires local access and user interaction and grants the resulting code the service's SYSTEM privileges, enabling full compromise of the Windows host.
The record
- CVE
- CVE-2019-6834
- Published
- Mar 28, 2022
- Updated
- Aug 4, 2024
- Vendor
- Schneider Electric
- Product
- Schneider Electric Software Update (SESU) – SUT Service component
- Classifications
- CWE-502, T1203
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 28, 2022CVE 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=V2.1.1 <=V2.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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