Recurring login crash via unvalidated proc path
Published Apr 8, 2020 · Updated Sep 16, 2024
Improper input validation in all Secdo versions for Windows allows local users to crash the system on every login through disk-root access. Secdo fails to validate the root-level C:\proc path before using it during login, so attacker-controlled folder state triggers the crash. Exploitation requires an authenticated local account with create-folder or append-data access at C:; the reported effect is availability loss only.
Summary
What happened
Improper input validation in all Secdo versions for Windows allows local users to crash the system on every login through disk-root access. Secdo fails to validate the root-level C:\proc path before using it during login, so attacker-controlled folder state triggers the crash. Exploitation requires an authenticated local account with create-folder or append-data access at C:; the reported effect is availability loss only.
The record
- CVE
- CVE-2020-1986
- Published
- Apr 8, 2020
- Updated
- Sep 16, 2024
- Vendor
- Secdo
- Product
- Secdo
- Classifications
- CWE-20, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 8, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 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=all versions
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Public exploit references
No public exploit references are available in this record.
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