dbcve.org
SourcetreeApplication · Atlassian

CVE-2024-21697

HIGH · 8.8 CVSS v3.1 Published 2024-11-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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 versions 4.2.8 of Sourcetree for Mac and 3.4.19 for Sourcetree for Windows. This RCE (Remote Code Execution) vulnerability, with a CVSS Score of 8.8, 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 4.2: Upgrade to a release greater than or equal to 4.2.9 Sourcetree for Windows 3.4: Upgrade to a release greater than or equal to 3.4.20 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 Remote Code Execution (RCE) vulnerability in Atlassian's Sourcetree Git client. The vulnerability allows an unauthenticated attacker to execute arbitrary code through unspecified means in the application, with high impact across confidentiality, integrity, and availability. User interaction is required for exploitation.

MitigationUpgrade Sourcetree for Mac to version 4.2.9 or later, and Sourcetree for Windows to version 3.4.20 or later, as specified in the vendor advisory.

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.19= 4.2.8

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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. Confirm Sourcetree is installed
    Locate the Sourcetree application on your system. On Windows, check Program Files or the Start menu. On Mac, check the Applications folder. If the application is not present, you are not affected.
    Affected if Sourcetree is installed on the system
  2. Identify the installed version on Windows
    Open Sourcetree and navigate to the 'About Sourcetree' option (typically found in the Help menu). The version number displayed in the dialog is your installed version. Alternatively, check the Windows Programs and Features list for the installed version.
    Affected if The version displayed is exactly 3.4.19
  3. Identify the installed version on Mac
    Open Sourcetree and navigate to the 'About Sourcetree' option (in the Sourcetree menu). The version number displayed in the dialog is your installed version. Alternatively, right-click Sourcetree in the Applications folder, select 'Get Info', and note the version listed.
    Affected if The version displayed is exactly 4.2.8
  4. Compare against affected versions
    If you have determined your installed version, compare it numerically to the affected versions: 3.4.19 (Windows) and 4.2.8 (Mac). Only exact version matches are affected; later versions are not vulnerable.
    Affected if Your installed version matches exactly 3.4.19 on Windows or 4.2.8 on Mac

You are affected only if the exact installed version of Sourcetree is 3.4.19 (Windows) or 4.2.8 (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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Sourcetree for Mac to version 4.2.9 or later, and Sourcetree for Windows to version 3.4.20 or later, as specified in the vendor advisory.

Recommended fix High confidence

Sourcetree for Mac >= 4.2.9; Sourcetree for Windows >= 3.4.20

  1. Navigate to the official Sourcetree download center at https://www.sourcetreeapp.com/download-archives
  2. Download the latest version of Sourcetree for your operating system (Mac or Windows)
  3. Install the new version, ensuring you receive version 4.2.9 or higher for Mac, or version 3.4.20 or higher for Windows
  4. After installation, verify the installed version matches or exceeds the minimum fixed version for your platform

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
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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