A vulnerability, which was classified as critical, has been found in SourceTree up to 2.5.4.x on Windows. This issue affects some unknown functionality. The manipulation as part of a Argument leads to a command injection vulnerability. Using CWE to declare the problem leads to CWE-77. The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

There was an argument injection vulnerability in Sourcetree for Windows via Mercurial repository tag name that is going to be deleted. An attacker with permission to create a tag on a Mercurial repository linked in Sourcetree for Windows is able to exploit this issue to gain code execution on the system. All versions of Sourcetree for Windows before 2.5.5.0 are affected by this vulnerability.

The bug was discovered 04/04/2018. The weakness was shared 04/25/2018 (Website). It is possible to read the advisory at jira.atlassian.com. The identification of this vulnerability is CVE-2018-5226 since 01/05/2018. The exploitation is known to be easy. The attack may be initiated remotely. A simple authentication is required for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1202 according to MITRE ATT&CK.

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

Upgrading to version 2.5.5.0 eliminates this vulnerability.

Productinfo

Name

• SourceTree

Version

• 2.5.0
• 2.5.1
• 2.5.2
• 2.5.3
• 2.5.4

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion