dbcve.org
SourcetreeApplication · Atlassian

CVE-2023-22514

HIGH · 7.8 CVSS v3.1 Published 2024-01-16
Fix available
A fix is available. Upgrade to 3.4.15 / 4.2.5 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
This High severity RCE (Remote Code Execution) vulnerability was introduced in version 3.4.14 of Sourcetree for Mac and Sourcetree for Windows. This RCE (Remote Code Execution) vulnerability, with a CVSS Score of 7.8, and a CVSS Vector of: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H which allows an unauthenticated attacker to execute arbitrary code which has high impact to confidentiality, high impact to integrity, high impact to availability, and requires user interaction. Atlassian recommends that Sourcetree for Mac and Sourcetree for Windows customers upgrade to latest version, if you are unable to do so, upgrade your instance to one of the specified supported fixed versions: Sourcetree for Mac and Sourcetree for Windows 3.4: Upgrade to a release greater than or equal to 3.4.15 See the release notes (https://www.sourcetreeapp.com/download-archives). You can download the latest version of Sourcetree for Mac and Sourcetree for Windows from the download center (https://www.sourcetreeapp.com/download-archives). This vulnerability was reported via our Penetration Testing program.

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 a high-severity Remote Code Execution (RCE) vulnerability in Sourcetree for Mac and Windows introduced in version 3.4.14. The vulnerability has a CVSS score of 7.8 with a local attack vector (AV:L), low complexity (AC:L), no privileges required (PR:N), but requires user interaction (UI:R). An unauthenticated attacker can execute arbitrary code with high impact to confidentiality, integrity, and availability.

MitigationUpgrade Sourcetree for Mac and Windows to version 3.4.15 or later to remediate this RCE 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:>= 3.4.0, < 3.4.15>= 4.1.0, < 4.2.5

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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
    On Windows, look for Sourcetree in Program Files or check the Start menu. On Mac, check /Applications folder or use Spotlight to search for Sourcetree.
    Affected if Sourcetree is present on the system
  2. Identify the installed version on Windows
    Open Sourcetree, then go to Help > About Sourcetree to view the version number. Alternatively, check the Windows registry or the executable properties.
    Affected if The displayed version is 3.4.0 through 3.4.14, or 4.1.0 through 4.2.4
  3. Identify the installed version on Mac
    Open Sourcetree, then go to Sourcetree menu > About Sourcetree to view the version number.
    Affected if The displayed version is 3.4.0 through 3.4.14, or 4.1.0 through 4.2.4
  4. Compare version against affected ranges
    If you have command-line access, you can also check version info from the application executable or package metadata.
    Affected if Your installed version matches 3.4.x where x is 0-14, or 4.1.x where x is 0-4, or 4.2.x where x is 0-4

You are affected if Sourcetree is installed and the version falls within 3.4.0-3.4.14 or 4.1.0-4.2.4 on either Windows or Mac.

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 3.4.15 / 4.2.5 or later
Fixed in 3.4.154.2.5
Interim mitigation

Upgrade Sourcetree for Mac and Windows to version 3.4.15 or later to remediate this RCE vulnerability.

Recommended fix High confidence

Sourcetree 4.2.5 or later (or 3.4.15+ for the 3.4.x branch)

  1. Navigate to the official Sourcetree download page at https://www.sourcetreeapp.com/download-archives
  2. Download the latest version of Sourcetree for your platform (Mac or Windows)
  3. Close any running instances of Sourcetree
  4. Install the downloaded version by following the on-screen installation prompts
  5. Restart Sourcetree after installation completes
  6. Alternatively, if you must stay on the 3.4.x branch, download and install version 3.4.15 or later
  7. Verify the installed version by checking About Sourcetree in the application menu
Caveat Review release notes for any configuration or workflow changes between your current version and the upgrade target

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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