SourcetreeApplication · Atlassian
CVE-2017-14593
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSourcetree for Windows had several argument and command injection bugs in Mercurial and Git repository handling. An attacker with permission to commit to a repository linked in Sourcetree for Windows is able to exploit this issue to gain code execution on the system. From version 0.8.4b of Sourcetree for Windows, this vulnerability can be triggered from a webpage through the use of the Sourcetree URI handler. Versions of Sourcetree for Windows starting with 0.5.1.0 before version 2.4.7.0 are affected by this vulnerability
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSourcetree for Windows versions 0.5.1.0 through before 2.4.7.0 contain multiple argument and command injection vulnerabilities in Mercurial and Git repository handling. An attacker with commit permissions to a linked repository can inject malicious commands that execute with the privileges of the Sourcetree process. From version 0.8.4b, this can be triggered remotely via the Sourcetree URI handler from malicious webpages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SourcetreeApplication
>= 0.5.1.0, < 2.4.7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate Sourcetree executableNavigate to C:\Program Files\Atlassian\SourceTree\ and locate SourceTree.exe, or search for SourceTree.exe using Windows Explorer searchAffected if File exists on the system
-
Check installed versionRight-click SourceTree.exe, select Properties, then go to the Details tab and read the Product version fieldAffected if Version displays as 0.5.1.0 through 2.4.6.x (any version >= 0.5.1.0 but < 2.4.7.0)
-
Verify via Windows Programs and FeaturesOpen Control Panel > Programs and Features, locate Atlassian Sourcetree in the list, and note the version shown in the Version columnAffected if Version shows 0.5.1.0 or higher but lower than 2.4.7.0
-
Alternative: Check via command lineOpen Command Prompt and run: wmic product where "name like '%Sourcetree%'" get name,versionAffected if Version returned is >= 0.5.1.0 and < 2.4.7.0
The system is affected if Sourcetree for Windows is installed with any version from 0.5.1.0 up to and including 2.4.6.x, regardless of configuration or repository linkage settings.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data2.4.7.0
Upgrade Sourcetree for Windows to version 2.4.7.0 or later. Until patched, avoid linking repositories from untrusted sources and exercise caution when clicking sourcetree:// URIs from untrusted webpages.
Fix this in Sourcetree
Scoped from the published advisory
- Consultation1.0 h
- Implementation0.5 h
- Testing0.5 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14593 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-14593 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data