SourcetreeApplication · Atlassian

CVE-2018-13396

HIGH · 8.8 CVSS v3.0 Published 2018-11-05
Fix available
A fix is available. Upgrade to 3.0.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 from version 1.0b2 before version 3.0.0 via Git subrepositories 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.

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

Argument injection vulnerability in Sourcetree for macOS (versions 1.0b2 to before 3.0.0) allows authenticated users with commit permissions to Mercurial repositories to execute arbitrary code via maliciously crafted Git subrepository configurations.

MitigationUpgrade Sourcetree for macOS to version 3.0.0 or later to remediate this vulnerability.

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, < 3.0.0= 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
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 checks

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

  1. Confirm Sourcetree for macOS is installed
    Check for the application at /Applications/Sourcetree.app or search using 'mdfind kMDItemFSName == "Sourcetree.app"' in Terminal
    Affected if The application exists in the system
  2. Determine installed Sourcetree version
    Run 'defaults read /Applications/Sourcetree.app/Contents/Info CFBundleShortVersionString' in Terminal to retrieve the version number
    Affected if Version is 1.0b2 or higher but lower than 3.0.0
  3. Verify user works with Mercurial repositories
    Check if any .hg directories exist in user repositories or look for Mercurial repository folders marked with Sourcetree's Hg icon in the application
    Affected if The user has cloned or manages Mercurial repositories using Sourcetree
  4. Inspect Git subrepository configurations
    Look for .gitmodules files within Mercurial repositories in the user's workspace, as the vulnerability exploits maliciously crafted Git subrepository settings
    Affected if .gitmodules files exist within Mercurial repositories and those repositories are managed by the affected Sourcetree version

User is affected if Sourcetree for macOS version 1.0b2 through 2.x is installed and the user manages Mercurial repositories containing Git subrepository configurations.

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.

From vendor data
Upgrade available Upgrade to 3.0.0 or later
Fixed in 3.0.0
Interim mitigation

Upgrade Sourcetree for macOS to version 3.0.0 or later to remediate this vulnerability.

Fix this in Sourcetree Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
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,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-13396 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