Secdo: Privilege escalation via hardcoded script path
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Secdo | Secdo | affected |
|
Configuration 1 [-]
| AND |
|
No data.
No data available yet.
Vendor Solution
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.
Vendor Workaround
This issue can be mitigated by : - Ensure unprivileged users do not have 'create folder' access on the root of filesystem such as C:\. or - Creating a folder named C:\Common and ensuring unprivileged users do not have 'create folder' access.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2020-12774 | 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. |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.311% probability within 30 days)
Key SSVC decision points have not yet been added.
| Link | Providers |
|---|---|
| https://security.paloaltonetworks.com/CVE-2020-1984 |
|
No history.