CVE-2016-20056 | Spy-Emergency Spy Emergency 23.0.205 SpyEmrgSrv Service unquoted search path (Exploit 40550 / EDB-40550)

VDB-355364 · CVE-2016-20056 · EXPLOIT 40550 SPY-EMERGENCY SPY EMERGENCY 23.0.205 SPYEMRGSRV SERVICE UNQUOTED SEARCH PATH HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 7.1 $0-$5k 2.04- Summaryinfo A vulnerability, which was classified as problematic, was found in Spy-Emergency Spy Emergency 23.0.205. This impacts an unknown function of the component SpyEmrgSrv Service. Such manipulation leads to unquoted search path. This vulnerability is traded as CVE-2016-20056. An attack has to be approached locally. Furthermore, there is an exploit available. Detailsinfo A vulnerability was found in Spy-Emergency Spy Emergency 23.0.205. It has been rated as critical. Affected by this issue is some unknown functionality of the component SpyEmrgSrv Service. The manipulation with an unknown input leads to a unquoted search path vulnerability. Using CWE to declare the problem leads to CWE-428. The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path. Impacted is confidentiality, integrity, and availability. CVE summarizes: Spy Emergency build 23.0.205 contains an unquoted service path vulnerability in the SpyEmrgHealth and SpyEmrgSrv services that allows local attackers to escalate privileges by inserting malicious executables. Attackers can place executable files in the unquoted service path and trigger service restart or system reboot to execute code with LocalSystem privileges. The weakness was shared by Amir.ght as 40550. The advisory is shared for download at exploit-db.com. This vulnerability is handled as CVE-2016-20056 since 04/04/2026. The exploitation is known to be difficult. The attack needs to be approached locally. Technical details are unknown but a public exploit is available. The MITRE ATT&CK project declares the attack technique as T1574.009. The exploit is available at exploit-db.com. It is declared as proof-of-concept. There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product. The vulnerability is also documented in the databases at Exploit-DB (40550) and EUVD (EUVD-2016-10863). Productinfo Vendor Spy-Emergency Name Spy Emergency Version 23.0.205 CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 7.4 VulDB Meta Temp Score: 7.1 VulDB Base Score: 7.0 VulDB Temp Score: 6.4 VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA Base Score: 7.8 CNA Vector (VulnCheck): 🔒 CVSSv2info Vector Complexity Authentication Confidentiality Integrity Availability Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock Unlock VulDB Base Score: 🔒 VulDB Temp Score: 🔒 VulDB Reliability: 🔍 Exploitinginfo Class: Unquoted search path CWE: CWE-428 / CWE-426 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: No Availability: 🔒 Access: Public Status: Proof-of-Concept Download: 🔒 Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Exploit-DB: 🔒 Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 04/04/2026 Advisory disclosed 04/04/2026 +0 days CVE reserved 04/04/2026 +0 days VulDB entry created 04/05/2026 +0 days VulDB entry last update Sourcesinfo Advisory: 40550 Researcher: Amir.ght Status: Not defined CVE: CVE-2016-20056 (🔒) GCVE (CVE): GCVE-0-2016-20056 GCVE (VulDB): GCVE-100-355364 EUVD: 🔒 scip Labs: https://www.scip.ch/en/?labs.20161013 Entryinfo Created: 04/04/2026 19:47 Updated: 04/05/2026 01:03 Changes: 04/04/2026 19:47 (80), 04/05/2026 01:03 (1) Complete: 🔍 Cache ID: 99:F9F:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸