Tiki 17.1 CSV CMD.EXE Special Char injection

Summaryinfo

A vulnerability described as critical has been identified in Tiki 17.1. The impacted element is an unknown function of the file CMD.EXE of the component CSV Handler. Executing a manipulation with the input =cmd|' /C calc'!A0 as part of Special Char can lead to injection. This vulnerability is tracked as CVE-2018-7304. The attack can be launched remotely. No exploit exists.

Detailsinfo

A vulnerability has been found in Tiki 17.1 and classified as critical. This vulnerability affects an unknown code block of the file CMD.EXE of the component CSV Handler. The manipulation with the input value =cmd|' /C calc'!A0 leads to a injection vulnerability. The CWE definition for the vulnerability is CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Tiki 17.1 does not validate user input for special characters; consequently, a CSV Injection attack can open a CMD.EXE or Calculator window on the victim machine to perform malicious activity, as demonstrated by an "=cmd|' /C calc'!A0" payload during User Creation.

The bug was discovered 01/18/2018. The weakness was disclosed 02/21/2018 (Website). The advisory is shared for download at websecnerd.blogspot.in. This vulnerability was named CVE-2018-7304 since 02/21/2018. The attack can be initiated remotely. The requirement for exploitation is a single authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1055.

The vulnerability was handled as a non-public zero-day exploit for at least 34 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The entries VDB-113690 and VDB-113691 are pretty similar. Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Tiki

Version

• 17.1

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion