Sourcetree vulnerabilitiesRanked by how likely they are to be used.
Sourcetree is made by Atlassian. We track 14 published vulnerabilities in it, across 355 versions. None of them is on the list of flaws known to be exploited today. If you run Sourcetree, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Sourcetree vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Sourcetree's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Sourcetree flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 8.3%CVE-2017-8768Critical
Atlassian SourceTree v2.5c and prior are affected by a command injection in the handling of the sourcetree:// scheme.
- 6.7%CVE-2018-20235High
There was an argument injection vulnerability in Atlassian Sourcetree for Windows from version 0.5a before version 3.0.15 via filenames in Mercurial repositories.
- 6.4%CVE-2018-20236High
There was an command injection vulnerability in Sourcetree for Windows from version 0.5a before version 3.0.10 via URI handling.
- 5.9%CVE-2018-20234High
There was an argument injection vulnerability in Atlassian Sourcetree for macOS from version 1.2 before version 3.1.1 via filenames in Mercurial repositories.
- 5.5%CVE-2017-14592High
Sourcetree for macOS had several argument and command injection bugs in Mercurial and Git repository handling.
- 5.5%CVE-2017-14593High
Sourcetree for Windows had several argument and command injection bugs in Mercurial and Git repository handling.
- 4.9%CVE-2019-11582High
An argument injection vulnerability in Atlassian Sourcetree for Windows's URI handlers, in all versions prior to 3.1.3, allows remote attackers to gain remote code execution through the use of a crafted URI.
- 2.2%CVE-2018-13385Critical
There was an argument injection vulnerability in Sourcetree for macOS via filenames in Mercurial repositories.
- 1.9%CVE-2018-13396High
There was an argument injection vulnerability in Sourcetree for macOS from version 1.0b2 before version 3.0.0 via Git subrepositories in Mercurial repositories.
- 1.9%CVE-2018-13397High
There was an argument injection vulnerability in Sourcetree for Windows from version 0.5.1.0 before version 3.0.0 via Git subrepositories in Mercurial repositories.
Running Sourcetree? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Atlassian SourceTree v2.5c and prior are affected by a command injection in the handling of the sourcetree:// scheme. It will lead to arbitrary OS command execution with a URL substring of sourcetree://cloneRepo/ext:: or sourcetree://checkoutRef/ext:: followed by the command. The Atlassian ID number is SRCTREE-4632.
- Matched to
- Sourcetree on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 14 published vulnerabilities listed under the name Sourcetree, across 355 versions.
None of Sourcetree's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Sourcetree. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.