CVE-2020-37061
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-37061 is a high-severity Unquoted Search Path or Element (CWE-428) vulnerability in Weird Solutions (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 2th 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-37061 is an unquoted service path vulnerability affecting BOOTP Turbo version 2.0.1214. The issue stems from an improperly quoted executable path in the service configuration, classified under CWE-428, which enables local attackers to potentially execute arbitrary code with elevated system privileges. The vulnerability carries 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 impact potential from local access.
A local attacker with low privileges can exploit this vulnerability by placing a malicious executable in a directory that precedes the legitimate service binary in the system's search path. When the BOOTP Turbo service starts under LocalSystem permissions, the system may execute the attacker's malicious code instead, achieving full control over the system with high confidentiality, integrity, and availability impacts.
Advisories and related resources, including a public exploit, are documented at https://www.exploit-db.com/exploits/48078, https://www.vulncheck.com/advisories/bootp-turbo-bootp-turbo-unquoted-service-path, and https://www.weird-solutions.com. Security practitioners should review these for detailed mitigation steps, such as reconfiguring the service path with proper quoting or restricting service execution contexts.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-30968
Vulnerability Data
BOOTP Turbo 2.0.1214 contains an unquoted service path vulnerability that allows local attackers to potentially execute arbitrary code with elevated system privileges. Attackers can exploit the unquoted executable path to inject malicious code that will be executed when the service…
more
starts with LocalSystem permissions.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Direct match to unquoted service path (CWE-428) enabling path interception for local privilege escalation via malicious binary placement.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Enforces secure configuration settings for system services, including proper quoting of executable paths to directly prevent unquoted service path vulnerabilities.
Mandates identification, reporting, and correction of flaws such as unquoted service paths through timely reconfiguration or patching.
Implements least privilege for services running with elevated permissions, reducing the impact of privilege escalation from malicious code executed via unquoted paths.
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.