SourcetreeApplication · Atlassian
CVE-2018-13386
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 · uneditedThere was an argument injection vulnerability in Sourcetree for Windows via filenames in Mercurial repositories. An attacker with permission to commit to a Mercurial repository linked in Sourcetree for Windows is able to exploit this issue to gain code execution on the system. Versions of Sourcetree for Windows before version 2.6.9 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 confidenceAn argument injection vulnerability exists in Sourcetree for Windows through Mercurial repository filenames. An attacker with commit access to a linked Mercurial repository can craft malicious filenames that inject arguments into Mercurial commands, leading to arbitrary code execution on the affected system.
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
< 2.6.9CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Sourcetree for Windows installationLook for Sourcetree in the Windows Start Menu, or check for its executable at typical installation paths such as C:\Program Files\Atlassian\SourceTree\SourceTree.exe or C:\Program Files (x86)\Atlassian\SourceTree\SourceTree.exeAffected if Sourcetree for Windows is not installed on the system
-
Identify the installed versionRight-click the SourceTree.exe file, select Properties, then click the Details tab to view the Product version fieldAffected if The version shown is lower than 2.6.9 (for example, 2.6.8, 2.6.7, 2.5.x, etc.)
-
Verify Mercurial repository usageOpen Sourcetree and check the repositories panel for any Mercurial (hg) repositories. Also check the options menu under Tools > Options > General for Mercurial repository settingsAffected if One or more Mercurial repositories are configured or linked in Sourcetree
-
Confirm commit access to Mercurial repositoriesReview repository settings in Sourcetree to see if push or commit operations are enabled, or check with repository administrators about who has commit or push accessAffected if The user or any account has commit or push access to a linked Mercurial repository
If Sourcetree for Windows is installed with a version below 2.6.9 AND Mercurial repositories with commit/push access are configured, the environment is vulnerable to argument injection via malicious filenames.
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.6.9
Upgrade Sourcetree for Windows to version 2.6.9 or later. Until upgraded, avoid cloning untrusted Mercurial repositories and limit commit access to trusted users only.
Fix this in Sourcetree
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13386 — 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-2018-13386 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