dbcve.org
SourcetreeApplication · Atlassian

CVE-2017-8768

CRITICAL · 9.8 CVSS v3.0 Published 2017-05-04
Fix available
A fix is available. Upgrade to after 2.5c or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

Atlassian SourceTree versions 2.5c and prior contain a command injection vulnerability in the handling of the sourcetree:// URL scheme. Specifically, the cloneRepo/ext:: and checkoutRef/ext:: parameters allow attackers to inject arbitrary OS commands that execute with the privileges of the user running SourceTree when they interact with a maliciously crafted URL.

MitigationUpgrade SourceTree to a version newer than 2.5c. Until patched, users should avoid clicking untrusted sourcetree:// links and organizations may consider disabling the URL handler as a temporary measure.

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
Affected:<= 2.5c

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if SourceTree is installed
    Look for SourceTree application in the system (Windows: Program Files or Program Files (x86), Mac: /Applications)
    Affected if SourceTree application exists on the system
  2. Determine the installed SourceTree version
    Open SourceTree and navigate to the About or Check for Updates dialog to view the exact version number
    Affected if The version number is 2.5c or any version lower than 2.5c
  3. Verify the sourcetree:// URL handler is registered
    Check system registry (Windows) or defaults read (Mac) for sourcetree:// URL scheme handler registration
    Affected if The sourcetree:// URL scheme handler is present and enabled in the system
  4. Confirm SourceTree is set as the default handler for sourcetree:// URLs
    Check system settings to see if SourceTree is registered as the handler for sourcetree:// protocol
    Affected if SourceTree is the registered handler for sourcetree:// URLs and the version is <= 2.5c

A user is affected if SourceTree version 2.5c or prior is installed AND the sourcetree:// URL scheme handler is enabled, making the application vulnerable to command injection via maliciously crafted URLs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.5c
Interim mitigation

Upgrade SourceTree to a version newer than 2.5c. Until patched, users should avoid clicking untrusted sourcetree:// links and organizations may consider disabling the URL handler as a temporary measure.

Recommended fix Moderate confidence

Latest SourceTree release (version newer than 2.5c)

  1. 1. Close any running instances of SourceTree
  2. 2. Back up your SourceTree settings and repositories (optional but recommended)
  3. 3. Download the latest version of SourceTree from the official Atlassian website at https://www.sourcetreeapp.com/
  4. 4. Install the new version, overwriting the existing installation
  5. 5. Launch SourceTree and verify the application runs without errors
  6. 6. Test that sourcetree:// URLs are handled correctly and no longer allow command injection

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sourcetree Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing4.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8768 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-8768 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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