Kite up to 1.2020.1119.0 KiteService Windows Service KiteService.exe unquoted search path

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Kite up to 1.2020.1119.0. This vulnerability affects unknown code of the file C:\Program Files\Kite\KiteService.exe of the component KiteService Windows Service. The manipulation leads to unquoted search path. This vulnerability is uniquely identified as CVE-2020-36958. Local access is required to approach this attack. Moreover, an exploit is present.

Detailsinfo

A vulnerability was found in Kite up to 1.2020.1119.0. It has been rated as critical. This issue affects an unknown functionality of the file C:\Program Files\Kite\KiteService.exe of the component KiteService Windows 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. The summary by CVE is:

Kite 1.2020.1119.0 contains an unquoted service path vulnerability in the KiteService Windows service that allows local attackers to potentially execute arbitrary code. Attackers can exploit the unquoted path in 'C:\Program Files\Kite\KiteService.exe' to inject malicious executables and escalate privileges on the system.

The weakness was disclosed by Ismael Nava as 49205. The advisory is shared at exploit-db.com. The identification of this vulnerability is CVE-2020-36958 since 01/26/2026. The exploitation is known to be difficult. An attack has to be approached locally. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1574.009 for this issue.

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 vulnerability database at Exploit-DB (49205). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Kite

Version

• 1.2020.1119

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion