CVE-2020-37037
Raw vector
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2020-37037 is a high-severity Unquoted Search Path or Element (CWE-428) vulnerability in Avast SecureLine (inferred from references). Its CVSS base score is 8.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Path Interception by Unquoted Path (T1574.009); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to CM-6 (Configuration Settings) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2020-37037 is an unquoted service path vulnerability (CWE-428) affecting Avast SecureLine version 5.5.522.0. The flaw exists in the service configuration, where the unquoted path allows local users to potentially execute arbitrary code with elevated system privileges. This issue has a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating high severity due to its potential for significant impact on confidentiality, integrity, and availability.
Local attackers with low privileges (PR:L) can exploit this vulnerability by placing a malicious executable in a directory that precedes the legitimate service binary in the system's search path. Upon service startup, the injected code executes with LocalSystem account permissions, enabling full system compromise, including unauthorized access to sensitive data, modification of system files, and disruption of services.
Advisories and related resources, including those from Vulncheck (https://www.vulncheck.com/advisories/avast-secureline-secureline-unquoted-service-path) and Avast (https://www.avast.com/), provide details on the issue. A proof-of-concept exploit is publicly available at Exploit-DB (https://www.exploit-db.com/exploits/48249), demonstrating practical exploitation.
In real-world context, the availability of a public exploit highlights the risk of active exploitation against unpatched systems running the affected Avast SecureLine version.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-30973
Vulnerability Data
Avast SecureLine 5.5.522.0 contains an unquoted service path vulnerability that allows local users to potentially execute code with elevated system privileges. Attackers can exploit the unquoted path in the service configuration to inject malicious code that would execute with LocalSystem…
more
account permissions during service startup.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Unquoted service path (CWE-428) directly enables path interception by unquoted path for local privilege escalation to SYSTEM via malicious binary placement.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Mandates secure configuration settings for services, including properly quoted executable paths, to directly prevent path hijacking exploits like CVE-2020-37037.
Requires timely identification, assessment, and remediation of flaws such as the unquoted service path in Avast SecureLine, preventing exploitation through patching.
Enforces least privilege for service accounts, limiting the impact of privilege escalation even if path hijacking occurs during service startup.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent path-handling flaws such as unquoted elements during development.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect unquoted search-path issues before deployment.
Enforcing controlled software installation can prevent unquoted search-path elements in executables and scripts.
Secure development lifecycle practices include input validation and path handling that reduce unquoted search-path weaknesses.
Secure system architecture and engineering principles require safe path construction and quoting conventions.
Secure coding standards directly mandate quoting search paths and avoiding unsafe path construction.
Change-management processes can enforce review of path-handling changes that might introduce unquoted elements.