CVE-2017-17405

Public Exploit

Description

Ruby before 2.4.3 allows Net::FTP command injection. Net::FTP#get, getbinaryfile, gettextfile, put, putbinaryfile, and puttextfile use Kernel#open to open a local file. If the localfile argument starts with the "|" pipe character, the command following the pipe character is executed. The default value of localfile is File.basename(remotefile), so malicious FTP servers could cause arbitrary command execution.

Category

8.8
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 89.94% Top 5%
Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory redhat.com Vendor Advisory debian.org Vendor Advisory redhat.com Vendor Advisory ruby-lang.org Vendor Advisory ruby-lang.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://access.redhat.com/errata/RHSA-2018:0585 third party advisory vendor advisory
https://lists.debian.org/debian-lts-announce/2017/12/msg00024.html third party advisory mailing list
https://access.redhat.com/errata/RHSA-2018:0378 third party advisory vendor advisory
http://www.securityfocus.com/bid/102204 vdb entry third party advisory
http://www.securitytracker.com/id/1042004 vdb entry third party advisory
https://www.ruby-lang.org/en/news/2017/12/14/net-ftp-command-injection-cve-2017-17405/ vendor advisory
https://www.exploit-db.com/exploits/43381/ exploit vdb entry third party advisory
https://access.redhat.com/errata/RHSA-2018:0584 third party advisory vendor advisory
https://www.ruby-lang.org/en/news/2017/12/14/ruby-2-4-3-released/ release notes patch vendor advisory
https://lists.debian.org/debian-lts-announce/2018/07/msg00012.html third party advisory mailing list
https://access.redhat.com/errata/RHSA-2018:0583 third party advisory vendor advisory
https://lists.debian.org/debian-lts-announce/2017/12/msg00025.html third party advisory mailing list
https://www.debian.org/security/2018/dsa-4259 third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2019:2806 vendor advisory

Frequently Asked Questions

What is the severity of CVE-2017-17405?
CVE-2017-17405 has been scored as a high severity vulnerability.
How to fix CVE-2017-17405?
To fix CVE-2017-17405, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-17405 being actively exploited in the wild?
It is possible that CVE-2017-17405 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~90% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.