Code execution via unsafe XML object decoding
Published Nov 21, 2024 · Updated Jul 5, 2026
Insecure deserialization in SciFiDryer ModbusMechanic 3.0 and earlier allows local users to execute code through a crafted XML file. The -bridge configuration path decodes XML instructions that instantiate an arbitrary Java ProcessBuilder and invoke its start method without restricting permitted classes. Exploitation requires the application to be launched with the attacker-controlled bridge file and executes commands with the launching user's privileges.
Summary
What happened
Insecure deserialization in SciFiDryer ModbusMechanic 3.0 and earlier allows local users to execute code through a crafted XML file. The -bridge configuration path decodes XML instructions that instantiate an arbitrary Java ProcessBuilder and invoke its start method without restricting permitted classes. Exploitation requires the application to be launched with the attacker-controlled bridge file and executes commands with the launching user's privileges.
The record
- CVE
- CVE-2024-51364
- Published
- Nov 21, 2024
- Updated
- Jul 5, 2026
- Vendor
- SciFiDryer
- Product
- ModbusMechanic
- Classifications
- CWE-434, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 21, 2024CVE publishedPublication date reported by the CVE source.
- Jul 5, 2026Record 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=0 <=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
- ModbusMechanic 3.0 Insecure Deserialization and RCE Proof of Conceptproof of concept · demonstrated
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