Security readout for executives and security teams
Plain-English summary
CVE-2020-1984 is a local privilege escalation in Secdo for Windows. If a lower-privileged authenticated user can write in the right place on the root OS disk, Secdo may run a script from a hardcoded path and elevate that user to SYSTEM privileges.
Executive priority
Treat this as a high-priority endpoint hardening and product-risk issue where Secdo remains deployed. It is not internet-routable, but it can turn an ordinary local account into SYSTEM, increasing impact after phishing, insider misuse, or workstation compromise.
Technical view
Secdo for Windows attempts to execute a script at a hardcoded path when present. The issue is classified as CWE-73 and affects all versions. Exploitation requires local authenticated access plus permission to create folders or append data at C:\, with the target path missing or writable.
Likely exposure
Exposure is limited to Windows systems running Secdo. Risk is highest where non-administrative users can create folders or append data at the root of C:\ and where the hardcoded execution path is absent or writable.
Exploitation context
The source bundle does not report active exploitation, and the CVE is not marked KEV. The attack is local, low complexity, requires low privileges, and needs no user interaction. Successful exploitation can affect confidentiality, integrity, and availability through SYSTEM-level access.
Researcher notes
Available evidence supports the vulnerability class, affected platform, prerequisites, and impact. The bundle does not provide exploit sightings, a specific patch level, or the hardcoded path value, so validation should avoid assumptions and rely on vendor guidance plus local permission review.
Mitigation direction
- Identify Windows endpoints running Secdo and prioritize them for review.
- Check Palo Alto Networks or vendor guidance for supported remediation.
- Restrict non-administrative create-folder and append-data permissions on C:\.
- Harden endpoint local access and monitor privileged process launches from Secdo.
- Plan replacement or compensating controls if no vendor fix is available.
Validation and detection
- Inventory Secdo installations on Windows endpoints.
- Review Secdo version and vendor advisory status.
- Audit C:\ root ACLs for non-administrative write-like permissions.
- Confirm whether the hardcoded execution path is absent or writable.
- Review endpoint telemetry for unusual Secdo-spawned SYSTEM activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-73: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2020-1984 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://security.paloaltonetworks.com/CVE-2020-1984CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
External Control of File Name or Path
External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.