Root code execution via unsafe Python eval
Published Feb 25, 2020 · Updated Aug 4, 2024
Improper code injection in Druva inSync Client 6.5.0 allows local authenticated attackers to execute arbitrary Python expressions. The inSyncDecommission daemon.set_file_acl method passes an unvalidated acl argument to Python eval() over a local RPC service on TCP port 6059. Authentication to the client is required, and successful exploitation runs attacker-supplied code with root privileges, enabling system and data compromise.
Summary
What happened
Improper code injection in Druva inSync Client 6.5.0 allows local authenticated attackers to execute arbitrary Python expressions. The inSyncDecommission daemon.set_file_acl method passes an unvalidated acl argument to Python eval() over a local RPC service on TCP port 6059. Authentication to the client is required, and successful exploitation runs attacker-supplied code with root privileges, enabling system and data compromise.
The record
- CVE
- CVE-2019-4000
- Published
- Feb 25, 2020
- Updated
- Aug 4, 2024
- Vendor
- Druva
- Product
- Druva inSync Client
- Classifications
- CWE-94, T1059.006
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 25, 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=6.5.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.
Weakness, pattern, technique
Public exploit references
- Tenable TRA-2020-12 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