First published: Wed Apr 08 2020(Updated: )
Secdo tries to execute a script at a hardcoded path if present, which allows a local authenticated user with 'create folders or append data' access to the root of the OS disk (C:\) to gain system privileges if the path does not already exist or is writable. This issue affects all versions of Secdo for Windows.
Credit: psirt@paloaltonetworks.com
Affected Software | Affected Version | How to fix |
---|---|---|
Palo Alto Networks Secdo | ||
Microsoft Windows Operating System |
This product is no longer supported and the issue is not going to be fixed. The issue can be completely mitigated by ensuring that unprivileged users do not have 'create folder' access on the root of the filesystem such as C:\ or on a folder named C:\Common.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-1984 has a high severity rating due to the potential for local authenticated users to gain system privileges.
To fix CVE-2020-1984, ensure that the paths used for script execution are not writable by unprivileged users.
All users of Palo Alto Networks Secdo are affected by CVE-2020-1984 if they use the vulnerable version.
A potential workaround for CVE-2020-1984 is to restrict access to the C:\ root directory for unauthorized users.
If you discover CVE-2020-1984 on your system, it is crucial to apply the latest security patches and ensure proper user permissions are configured.