Menu

Star on GitHub · 3.2k

CVE-2017-17405

8.8 · HIGH

Ruby before 2.4.3 allows Net::FTP command injection.

Published Dec 15, 2017CWE-78EPSS 73.83%

Overview

CVE-2017-17405 is a high-severity vulnerability. It was published on December 15, 2017 and has a CVSS 3.0 base score of 8.8 (HIGH).

This vulnerability has a CVSS 3.0 base score of 8.8, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2017-17405?

CVE-2017-17405 is a high-severity vulnerability. It was published on December 15, 2017 and has a CVSS 3.0 base score of 8.8 (HIGH).

How severe is CVE-2017-17405?

This vulnerability has a CVSS 3.0 base score of 8.8, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2017-17405?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2017-17405?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2017-17405 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2017

View all