dbcve.org
SourcetreeApplication · Atlassian

CVE-2018-13385

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-24
Fix available
A fix is available. Upgrade to 2.7.6 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
There was an argument injection vulnerability in Sourcetree for macOS via filenames in Mercurial repositories. An attacker with permission to commit to a Mercurial repository linked in Sourcetree for macOS is able to exploit this issue to gain code execution on the system. Versions of Sourcetree for macOS from 1.0b2 before 2.7.6 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 confidence

This is an argument injection vulnerability in Sourcetree for macOS where malicious filenames in Mercurial repositories can be crafted to inject and execute arbitrary code on the system. An attacker with commit permissions to a linked Mercurial repository can exploit this to achieve code execution.

MitigationUpdate Sourcetree for macOS to version 2.7.6 or later to patch the vulnerability. Additionally, restrict commit access to trusted personnel and implement code review processes for Mercurial repositories.

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:>= 1.0, < 2.7.6= 1.0

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. Verify Sourcetree for macOS is installed
    Open the Applications folder in Finder and look for 'Sourcetree' app, or run 'ls /Applications | grep -i sourcetree' in Terminal
    Affected if Sourcetree.app exists in the Applications folder
  2. Find the installed Sourcetree version
    Open Sourcetree, then go to Sourcetree menu > About Sourcetree to display the version number; alternatively, inspect the app bundle with 'defaults read /Applications/Sourcetree.app/Contents/Info.plist CFBundleShortVersionString'
    Affected if Version displayed is below 2.7.6
  3. Confirm Mercurial repository support is enabled
    Check if any Mercurial repositories are configured in Sourcetree: look for 'Hg' repository icons in the Repositories sidebar, or check for .hg folders in tracked project directories
    Affected if Mercurial repositories are present and active in Sourcetree
  4. Verify commit access to Mercurial repositories exists
    Review the repository settings in Sourcetree (Repository > Repository Settings) or check if the user has push/write permissions to any linked Mercurial remote
    Affected if User has commit or push access to any Mercurial repository linked in Sourcetree

A user is affected if they have Sourcetree for macOS version 1.0 through any version below 2.7.6 installed and actively use Mercurial repositories with commit access.

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 2.7.6 or later
Fixed in 2.7.6
Interim mitigation

Update Sourcetree for macOS to version 2.7.6 or later to patch the vulnerability. Additionally, restrict commit access to trusted personnel and implement code review processes for Mercurial repositories.

Recommended fix High confidence

Sourcetree for macOS 2.7.6 or later

  1. Open Sourcetree on macOS
  2. Check the current version by clicking Sourcetree menu > About Sourcetree
  3. If the version is less than 2.7.6, navigate to the Atlassian website to download Sourcetree for macOS version 2.7.6 or later
  4. Install the updated version of Sourcetree
  5. Restart the application if prompted

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

Fix this in Sourcetree Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-13385 — 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-2018-13385 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