Skip to content

SFTPGo has insufficient sanitization of user provided rsync command

High severity GitHub Reviewed Published Feb 7, 2025 in drakkan/sftpgo • Updated Feb 10, 2025

Package

gomod github.com/drakkan/sftpgo (Go)

Affected versions

<= 1.2.2

Patched versions

None
gomod github.com/drakkan/sftpgo/v2 (Go)
>= 0.9.5, <= 2.6.4
2.6.5

Description

Impact

SFTPGo supports execution of a defined set of commands via SSH. Besides a set of default commands some optional commands can be activated, one of them being rsync: it is disabled in the default configuration and it is limited to the local filesystem, it does not work with cloud/remote storage backends.

Due to missing sanitization of the client provided rsync command, an authenticated remote user can use some options of the rsync command to read or write files with the permissions of the SFTPGo server process.

Patches

This issue was fixed in version v2.6.5 by checking the client provided arguments.

drakkan/sftpgo@b347ab6

References

@drakkan drakkan published to drakkan/sftpgo Feb 7, 2025
Published to the GitHub Advisory Database Feb 7, 2025
Reviewed Feb 7, 2025
Published by the National Vulnerability Database Feb 7, 2025
Last updated Feb 10, 2025

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(12th percentile)

Weaknesses

CVE ID

CVE-2025-24366

GHSA ID

GHSA-vj7w-3m8c-6vpx

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.