CVE-2020-17381
About
An issue was discovered in Ghisler Total Commander 9.51. Due to insufficient access restrictions in the default installation directory, an attacker can elevate privileges by replacing the %SYSTEMDRIVE%\totalcmd\TOTALCMD64.EXE binary.
Rainforest analyst review
The weakness is insecure default permissions on Total Commander's install directory: a local attacker can replace the TOTALCMD64.EXE binary, and when another user later runs it, the attacker's code executes with that user's privileges. It's a classic write-then-wait escalation, gated on local access and someone actually launching the trojaned executable.
Because it requires both local presence and user interaction, this is a post-access escalation technique rather than an entry point. The realistic setting is a shared or multi-user machine where a low-privilege user can tamper with a binary that a higher-privilege user runs.
For perimeter prioritization we rank this down, it offers an attacker nothing remotely. Where it earns attention is on shared endpoints, and the practical checks are inventorying affected installs and verifying the directory ACLs that make the swap possible.
References
Related CVEs
Frequently asked questions
What is CVE-2020-17381?
An issue was discovered in Ghisler Total Commander 9.51. Due to insufficient access restrictions in the default installation directory, an attacker can elevate privileges by replacing the %SYSTEMDRIVE%\totalcmd\TOTALCMD64.EXE binary.
How severe is CVE-2020-17381?
CVE-2020-17381 carries a CVSS 3.1 base score of 7.3, rated high. On the Rainforest Risk Index — which weighs the severity alongside how easy the flaw is to reach and how broad its impact is — it scores 65 out of 100, in the elevated band.
How is CVE-2020-17381 exploited?
According to the CVSS vector (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H): attack vector Local, attack complexity Low, privileges required Low, user interaction Required. Impact on confidentiality High, integrity High and availability High.
Which products are affected by CVE-2020-17381?
Public advisories list the following as affected: total commander. Check the references on this page for the exact versions each vendor confirms.
How do I fix CVE-2020-17381?
Apply the fix the vendor published — the references on this page link to the primary advisories and patches. When patching can't happen right away, reduce the exposure of the affected component and watch it for exploitation attempts. Rainforest customers see this vulnerability correlated to their own assets and prioritized by real exposure, not by score alone.
Empower Your Security Strategy with Rainforest
Discover vulnerabilities early, prioritize critical threats, and protect what truly matters. Rainforest streamlines your security operations, saving you time and reducing costs, so you can focus on what drives your business forward.