ID CVE-2017-1000254
Summary libcurl may read outside of a heap allocated buffer when doing FTP. When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. The simple fact that this has issue remained undiscovered for this long could suggest that malformed PWD responses are rare in benign servers. We are not aware of any exploit of this flaw. This bug was introduced in commit [415d2e7cb7](https://github.com/curl/curl/commit/415d2e7cb7), March 2005. In libcurl version 7.56.0, the parser always zero terminates the string but also rejects it if not terminated properly with a final double quote.
References
Vulnerable Configurations
  • Haxx libcurl 7.7
    cpe:2.3:a:haxx:libcurl:7.7
  • Haxx libcurl 7.7.1
    cpe:2.3:a:haxx:libcurl:7.7.1
  • Haxx libcurl 7.7.2
    cpe:2.3:a:haxx:libcurl:7.7.2
  • Haxx libcurl 7.7.3
    cpe:2.3:a:haxx:libcurl:7.7.3
  • Haxx libcurl 7.8
    cpe:2.3:a:haxx:libcurl:7.8
  • Haxx libcurl 7.8.1
    cpe:2.3:a:haxx:libcurl:7.8.1
  • Haxx libcurl 7.9
    cpe:2.3:a:haxx:libcurl:7.9
  • Haxx libcurl 7.9.1
    cpe:2.3:a:haxx:libcurl:7.9.1
  • Haxx libcurl 7.9.2
    cpe:2.3:a:haxx:libcurl:7.9.2
  • Haxx libcurl 7.9.3
    cpe:2.3:a:haxx:libcurl:7.9.3
  • Haxx libcurl 7.9.4
    cpe:2.3:a:haxx:libcurl:7.9.4
  • Haxx libcurl 7.9.5
    cpe:2.3:a:haxx:libcurl:7.9.5
  • Haxx libcurl 7.9.6
    cpe:2.3:a:haxx:libcurl:7.9.6
  • Haxx libcurl 7.9.7
    cpe:2.3:a:haxx:libcurl:7.9.7
  • Haxx libcurl 7.9.8
    cpe:2.3:a:haxx:libcurl:7.9.8
  • Haxx libcurl 7.10
    cpe:2.3:a:haxx:libcurl:7.10
  • Haxx libcurl 7.10.1
    cpe:2.3:a:haxx:libcurl:7.10.1
  • Haxx libcurl 7.10.2
    cpe:2.3:a:haxx:libcurl:7.10.2
  • Haxx libcurl 7.10.3
    cpe:2.3:a:haxx:libcurl:7.10.3
  • Haxx libcurl 7.10.4
    cpe:2.3:a:haxx:libcurl:7.10.4
  • Haxx libcurl 7.10.5
    cpe:2.3:a:haxx:libcurl:7.10.5
  • Haxx libcurl 7.10.6
    cpe:2.3:a:haxx:libcurl:7.10.6
  • Haxx libcurl 7.10.7
    cpe:2.3:a:haxx:libcurl:7.10.7
  • Haxx libcurl 7.10.8
    cpe:2.3:a:haxx:libcurl:7.10.8
  • Haxx libcurl 7.11.0
    cpe:2.3:a:haxx:libcurl:7.11.0
  • Haxx libcurl 7.11.1
    cpe:2.3:a:haxx:libcurl:7.11.1
  • Haxx libcurl 7.11.2
    cpe:2.3:a:haxx:libcurl:7.11.2
  • Haxx libcurl 7.12.0
    cpe:2.3:a:haxx:libcurl:7.12.0
  • Haxx libcurl 7.12.1
    cpe:2.3:a:haxx:libcurl:7.12.1
  • Haxx libcurl 7.12.2
    cpe:2.3:a:haxx:libcurl:7.12.2
  • Haxx libcurl 7.12.3
    cpe:2.3:a:haxx:libcurl:7.12.3
  • Haxx libcurl 7.13.0
    cpe:2.3:a:haxx:libcurl:7.13.0
  • Haxx libcurl 7.13.1
    cpe:2.3:a:haxx:libcurl:7.13.1
  • Haxx libcurl 7.13.2
    cpe:2.3:a:haxx:libcurl:7.13.2
  • Haxx libcurl 7.14.0
    cpe:2.3:a:haxx:libcurl:7.14.0
  • Haxx libcurl 7.14.1
    cpe:2.3:a:haxx:libcurl:7.14.1
  • Haxx libcurl 7.15.0
    cpe:2.3:a:haxx:libcurl:7.15.0
  • Haxx libcurl 7.15.1
    cpe:2.3:a:haxx:libcurl:7.15.1
  • Haxx libcurl 7.15.2
    cpe:2.3:a:haxx:libcurl:7.15.2
  • Haxx libcurl 7.15.3
    cpe:2.3:a:haxx:libcurl:7.15.3
  • Haxx libcurl 7.15.4
    cpe:2.3:a:haxx:libcurl:7.15.4
  • Haxx libcurl 7.15.5
    cpe:2.3:a:haxx:libcurl:7.15.5
  • Haxx libcurl 7.16.0
    cpe:2.3:a:haxx:libcurl:7.16.0
  • Haxx libcurl 7.16.1
    cpe:2.3:a:haxx:libcurl:7.16.1
  • Haxx libcurl 7.16.2
    cpe:2.3:a:haxx:libcurl:7.16.2
  • Haxx libcurl 7.16.3
    cpe:2.3:a:haxx:libcurl:7.16.3
  • Haxx libcurl 7.16.4
    cpe:2.3:a:haxx:libcurl:7.16.4
  • Haxx libcurl 7.17.0
    cpe:2.3:a:haxx:libcurl:7.17.0
  • Haxx libcurl 7.17.1
    cpe:2.3:a:haxx:libcurl:7.17.1
  • Haxx libcurl 7.18.0
    cpe:2.3:a:haxx:libcurl:7.18.0
  • Haxx libcurl 7.18.1
    cpe:2.3:a:haxx:libcurl:7.18.1
  • Haxx libcurl 7.18.2
    cpe:2.3:a:haxx:libcurl:7.18.2
  • Haxx libcurl 7.19.0
    cpe:2.3:a:haxx:libcurl:7.19.0
  • Haxx libcurl 7.19.1
    cpe:2.3:a:haxx:libcurl:7.19.1
  • Haxx libcurl 7.19.2
    cpe:2.3:a:haxx:libcurl:7.19.2
  • Haxx libcurl 7.19.3
    cpe:2.3:a:haxx:libcurl:7.19.3
  • Haxx libcurl 7.19.4
    cpe:2.3:a:haxx:libcurl:7.19.4
  • Haxx libcurl 7.19.5
    cpe:2.3:a:haxx:libcurl:7.19.5
  • Haxx libcurl 7.19.6
    cpe:2.3:a:haxx:libcurl:7.19.6
  • Haxx libcurl 7.19.7
    cpe:2.3:a:haxx:libcurl:7.19.7
  • Haxx libcurl 7.20.0
    cpe:2.3:a:haxx:libcurl:7.20.0
  • Haxx libcurl 7.20.1
    cpe:2.3:a:haxx:libcurl:7.20.1
  • Haxx libcurl 7.21.0
    cpe:2.3:a:haxx:libcurl:7.21.0
  • Haxx libcurl 7.21.1
    cpe:2.3:a:haxx:libcurl:7.21.1
  • Haxx libcurl 7.21.2
    cpe:2.3:a:haxx:libcurl:7.21.2
  • Haxx libcurl 7.21.3
    cpe:2.3:a:haxx:libcurl:7.21.3
  • Haxx libcurl 7.21.4
    cpe:2.3:a:haxx:libcurl:7.21.4
  • Haxx libcurl 7.21.5
    cpe:2.3:a:haxx:libcurl:7.21.5
  • Haxx libcurl 7.21.6
    cpe:2.3:a:haxx:libcurl:7.21.6
  • Haxx libcurl 7.21.7
    cpe:2.3:a:haxx:libcurl:7.21.7
  • Haxx libcurl 7.22.0
    cpe:2.3:a:haxx:libcurl:7.22.0
  • Haxx libcurl 7.23.0
    cpe:2.3:a:haxx:libcurl:7.23.0
  • Haxx libcurl 7.23.1
    cpe:2.3:a:haxx:libcurl:7.23.1
  • Haxx libcurl 7.24.0
    cpe:2.3:a:haxx:libcurl:7.24.0
  • Haxx libcurl 7.25.0
    cpe:2.3:a:haxx:libcurl:7.25.0
  • Haxx libcurl 7.26.0
    cpe:2.3:a:haxx:libcurl:7.26.0
  • Haxx libcurl 7.27.0
    cpe:2.3:a:haxx:libcurl:7.27.0
  • Haxx libcurl 7.28.0
    cpe:2.3:a:haxx:libcurl:7.28.0
  • Haxx libcurl 7.28.1
    cpe:2.3:a:haxx:libcurl:7.28.1
  • Haxx libcurl 7.29.0
    cpe:2.3:a:haxx:libcurl:7.29.0
  • Haxx libcurl 7.30.0
    cpe:2.3:a:haxx:libcurl:7.30.0
  • Haxx libcurl 7.31.0
    cpe:2.3:a:haxx:libcurl:7.31.0
  • Haxx libcurl 7.32.0
    cpe:2.3:a:haxx:libcurl:7.32.0
  • Haxx libcurl 7.33.0
    cpe:2.3:a:haxx:libcurl:7.33.0
  • Haxx libcurl 7.34.0
    cpe:2.3:a:haxx:libcurl:7.34.0
  • Haxx libcurl 7.35.0
    cpe:2.3:a:haxx:libcurl:7.35.0
  • Haxx libcurl 7.36.0
    cpe:2.3:a:haxx:libcurl:7.36.0
  • Haxx libcurl 7.37.0
    cpe:2.3:a:haxx:libcurl:7.37.0
  • Haxx libcurl 7.37.1
    cpe:2.3:a:haxx:libcurl:7.37.1
  • Haxx libcurl 7.38.0
    cpe:2.3:a:haxx:libcurl:7.38.0
  • Haxx libcurl 7.39
    cpe:2.3:a:haxx:libcurl:7.39
  • Haxx libcurl 7.40.0
    cpe:2.3:a:haxx:libcurl:7.40.0
  • Haxx libcurl 7.41.0
    cpe:2.3:a:haxx:libcurl:7.41.0
  • Haxx libcurl 7.42.0
    cpe:2.3:a:haxx:libcurl:7.42.0
  • Haxx libcurl 7.42.1
    cpe:2.3:a:haxx:libcurl:7.42.1
  • Haxx libcurl 7.43.0
    cpe:2.3:a:haxx:libcurl:7.43.0
  • Haxx libcurl 7.44.0
    cpe:2.3:a:haxx:libcurl:7.44.0
  • Haxx libcurl 7.45.0
    cpe:2.3:a:haxx:libcurl:7.45.0
  • Haxx libcurl 7.46.0
    cpe:2.3:a:haxx:libcurl:7.46.0
  • Haxx libcurl 7.47.0
    cpe:2.3:a:haxx:libcurl:7.47.0
  • Haxx libcurl 7.47.1
    cpe:2.3:a:haxx:libcurl:7.47.1
  • Haxx libcurl 7.48.0
    cpe:2.3:a:haxx:libcurl:7.48.0
  • Haxx libcurl 7.49.0
    cpe:2.3:a:haxx:libcurl:7.49.0
  • Haxx libcurl 7.49.1
    cpe:2.3:a:haxx:libcurl:7.49.1
  • Haxx libcurl 7.50.0
    cpe:2.3:a:haxx:libcurl:7.50.0
  • Haxx libcurl 7.50.1
    cpe:2.3:a:haxx:libcurl:7.50.1
  • Haxx libcurl 7.50.2
    cpe:2.3:a:haxx:libcurl:7.50.2
  • Haxx libcurl 7.50.3
    cpe:2.3:a:haxx:libcurl:7.50.3
  • Haxx libcurl 7.51.0
    cpe:2.3:a:haxx:libcurl:7.51.0
  • Haxx libcurl 7.52.0
    cpe:2.3:a:haxx:libcurl:7.52.0
  • Haxx libcurl 7.52.1
    cpe:2.3:a:haxx:libcurl:7.52.1
  • Haxx libcurl 7.53.0
    cpe:2.3:a:haxx:libcurl:7.53.0
  • Haxx libcurl 7.53.1
    cpe:2.3:a:haxx:libcurl:7.53.1
  • Haxx libcurl 7.54.0
    cpe:2.3:a:haxx:libcurl:7.54.0
  • Haxx libcurl 7.54.1
    cpe:2.3:a:haxx:libcurl:7.54.1
  • Haxx libcurl 7.55.0
    cpe:2.3:a:haxx:libcurl:7.55.0
  • Haxx libcurl 7.55.1
    cpe:2.3:a:haxx:libcurl:7.55.1
CVSS
Base: 5.0
Impact:
Exploitability:
CWE CWE-119
CAPEC
  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Overflow Buffers
    Buffer Overflow attacks target improper or missing bounds checking on buffer operations, typically triggered by input injected by an attacker. As a consequence, an attacker is able to write past the boundaries of allocated buffer regions in memory, causing a program crash or potentially redirection of execution as per the attackers' choice.
  • Client-side Injection-induced Buffer Overflow
    This type of attack exploits a buffer overflow vulnerability in targeted client software through injection of malicious content from a custom-built hostile service.
  • Filter Failure through Buffer Overflow
    In this attack, the idea is to cause an active filter to fail by causing an oversized transaction. An attacker may try to feed overly long input strings to the program in an attempt to overwhelm the filter (by causing a buffer overflow) and hoping that the filter does not fail securely (i.e. the user input is let into the system unfiltered).
  • MIME Conversion
    An attacker exploits a weakness in the MIME conversion routine to cause a buffer overflow and gain control over the mail server machine. The MIME system is designed to allow various different information formats to be interpreted and sent via e-mail. Attack points exist when data are converted to MIME compatible format and back.
  • Overflow Binary Resource File
    An attack of this type exploits a buffer overflow vulnerability in the handling of binary resources. Binary resources may include music files like MP3, image files like JPEG files, and any other binary file. These attacks may pass unnoticed to the client machine through normal usage of files, such as a browser loading a seemingly innocent JPEG file. This can allow the attacker access to the execution stack and execute arbitrary code in the target process. This attack pattern is a variant of standard buffer overflow attacks using an unexpected vector (binary files) to wrap its attack and open up a new attack vector. The attacker is required to either directly serve the binary content to the victim, or place it in a locale like a MP3 sharing application, for the victim to download. The attacker then is notified upon the download or otherwise locates the vulnerability opened up by the buffer overflow.
  • Buffer Overflow via Symbolic Links
    This type of attack leverages the use of symbolic links to cause buffer overflows. An attacker can try to create or manipulate a symbolic link file such that its contents result in out of bounds data. When the target software processes the symbolic link file, it could potentially overflow internal buffers with insufficient bounds checking.
  • Overflow Variables and Tags
    This type of attack leverages the use of tags or variables from a formatted configuration data to cause buffer overflow. The attacker crafts a malicious HTML page or configuration file that includes oversized strings, thus causing an overflow.
  • Buffer Overflow via Parameter Expansion
    In this attack, the target software is given input that the attacker knows will be modified and expanded in size during processing. This attack relies on the target software failing to anticipate that the expanded data may exceed some internal limit, thereby creating a buffer overflow.
  • Buffer Overflow in an API Call
    This attack targets libraries or shared code modules which are vulnerable to buffer overflow attacks. An attacker who has access to an API may try to embed malicious code in the API function call and exploit a buffer overflow vulnerability in the function's implementation. All clients that make use of the code library thus become vulnerable by association. This has a very broad effect on security across a system, usually affecting more than one software process.
  • Buffer Overflow in Local Command-Line Utilities
    This attack targets command-line utilities available in a number of shells. An attacker can leverage a vulnerability found in a command-line utility to escalate privilege to root.
nessus via4
  • NASL family Huawei Local Security Checks
    NASL id EULEROS_SA-2018-1330.NASL
    description According to the versions of the curl package installed, the EulerOS Virtualization installation on the remote host is affected by the following vulnerabilities : - It was found that libcurl did not safely parse FTP URLs when using the CURLOPT_FTP_FILEMETHOD method. An attacker, able to provide a specially crafted FTP URL to an application using libcurl, could write a NULL byte at an arbitrary location, resulting in a crash, or an unspecified behavior.(CVE-2018-1000120) - A NULL pointer dereference flaw was found in the way libcurl checks values returned by the openldap ldap_get_attribute_ber() function. A malicious LDAP server could use this flaw to crash a libcurl client application via a specially crafted LDAP reply.(CVE-2018-1000121) - A buffer over-read exists in curl 7.20.0 to and including curl 7.58.0 in the RTSP+RTP handling code that allows an attacker to cause a denial of service or information leakage(CVE-2018-1000122) - curl version curl 7.20.0 to and including curl 7.59.0 contains a Buffer Over-read vulnerability in denial of service that can result in curl can be tricked into reading data beyond the end of a heap based buffer used to store downloaded rtsp content.(CVE-2018-1000301) - curl version curl 7.20.0 to and including curl 7.59.0 contains a Buffer Over-read vulnerability in denial of service that can result in curl can be tricked into reading data beyond the end of a heap based buffer used to store downloaded rtsp content.(CVE-2016-9586) - libcurl may read outside of a heap allocated buffer when doing FTP. When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. The simple fact that this has issue remained undiscovered for this long could suggest that malformed PWD responses are rare in benign servers. We are not aware of any exploit of this flaw. This bug was introduced in commit [415d2e7cb7](https://github.com/curl/curl/commit/415d2e 7cb7), March 2005. In libcurl version 7.56.0, the parser always zero terminates the string but also rejects it if not terminated properly with a final double quote.(CVE-2017-1000254) - The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a string that ends with an '[' character.The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a string that ends with an '[' character.(CVE-2017-8817) Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-11-13
    plugin id 118418
    published 2018-10-26
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=118418
    title EulerOS Virtualization 2.5.0 : curl (EulerOS-SA-2018-1330)
  • NASL family MacOS X Local Security Checks
    NASL id MACOSX_SECUPD2017-005.NASL
    description The remote host is running Mac OS X 10.11.6 or Mac OS X 10.12.6 and is missing a security update. It is therefore, affected by multiple vulnerabilities affecting the following components : - apache - curl - IOAcceleratorFamily - IOKit - Kernel - OpenSSL - Screen Sharing Server
    last seen 2019-02-21
    modified 2018-07-14
    plugin id 105081
    published 2017-12-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=105081
    title macOS and Mac OS X Multiple Vulnerabilities (Security Update 2017-002 and 2017-005)
  • NASL family PhotonOS Local Security Checks
    NASL id PHOTONOS_PHSA-2017-0044_CURL.NASL
    description An update of the curl package has been released.
    last seen 2019-02-08
    modified 2019-02-07
    plugin id 121756
    published 2019-02-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=121756
    title Photon OS 1.0: Curl PHSA-2017-0044
  • NASL family Slackware Local Security Checks
    NASL id SLACKWARE_SSA_2017-279-01.NASL
    description New curl packages are available for Slackware 14.0, 14.1, 14.2, and -current to fix a security issue.
    last seen 2018-09-02
    modified 2018-01-26
    plugin id 103703
    published 2017-10-09
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=103703
    title Slackware 14.0 / 14.1 / 14.2 / current : curl (SSA:2017-279-01)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_CCACE707A8D811E7AC58B499BAEBFEAF.NASL
    description The cURL project reports : FTP PWD response parser out of bounds read libcurl may read outside of a heap allocated buffer when doing FTP. When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the PWD command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault.
    last seen 2019-02-21
    modified 2018-12-19
    plugin id 103666
    published 2017-10-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=103666
    title FreeBSD : cURL -- out of bounds read (ccace707-a8d8-11e7-ac58-b499baebfeaf)
  • NASL family Huawei Local Security Checks
    NASL id EULEROS_SA-2017-1288.NASL
    description According to the version of the curl packages installed, the EulerOS installation on the remote host is affected by the following vulnerability : - libcurl may read outside of a heap allocated buffer when doing FTP. When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. The simple fact that this has issue remained undiscovered for this long could suggest that malformed PWD responses are rare in benign servers. We are not aware of any exploit of this flaw. This bug was introduced in commit [415d2e7cb7](https://github.com/curl/curl/commit/415d2e 7cb7), March 2005. In libcurl version 7.56.0, the parser always zero terminates the string but also rejects it if not terminated properly with a final double quote.(CVE-2017-1000254) Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-11-14
    plugin id 104907
    published 2017-12-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=104907
    title EulerOS 2.0 SP2 : curl (EulerOS-SA-2017-1288)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2017-E8179C06FD.NASL
    description - fix out of bounds read in FTP PWD response parser (CVE-2017-1000254) Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-02-02
    plugin id 105992
    published 2018-01-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=105992
    title Fedora 27 : curl (2017-e8179c06fd)
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-3992.NASL
    description Several vulnerabilities have been discovered in cURL, an URL transfer library. The Common Vulnerabilities and Exposures project identifies the following problems : - CVE-2017-1000100 Even Rouault reported that cURL does not properly handle long file names when doing an TFTP upload. A malicious HTTP(S) server can take advantage of this flaw by redirecting a client using the cURL library to a crafted TFTP URL and trick it to send private memory contents to a remote server over UDP. - CVE-2017-1000101 Brian Carpenter and Yongji Ouyang reported that cURL contains a flaw in the globbing function that parses the numerical range, leading to an out-of-bounds read when parsing a specially crafted URL. - CVE-2017-1000254 Max Dymond reported that cURL contains an out-of-bounds read flaw in the FTP PWD response parser. A malicious server can take advantage of this flaw to effectively prevent a client using the cURL library to work with it, causing a denial of service.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 103715
    published 2017-10-09
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=103715
    title Debian DSA-3992-1 : curl - security update
  • NASL family PhotonOS Local Security Checks
    NASL id PHOTONOS_PHSA-2017-0045.NASL
    description An update of [go,curl,libtiff,systemd,bash] packages for PhotonOS has been released.
    last seen 2019-02-21
    modified 2019-02-07
    plugin id 111894
    published 2018-08-17
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=111894
    title Photon OS 2.0: Bash / Curl / Go / Libtiff / Systemd PHSA-2017-0045 (deprecated)
  • NASL family PhotonOS Local Security Checks
    NASL id PHOTONOS_PHSA-2017-0044.NASL
    description An update of [openvswitch,systemd,curl,mariadb,bash] packages for PhotonOS has been released.
    last seen 2019-02-21
    modified 2019-02-07
    plugin id 111893
    published 2018-08-17
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=111893
    title Photon OS 1.0: Bash / Curl / Mariadb / Openvswitch / Systemd PHSA-2017-0044 (deprecated)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_SU-2017-3176-1.NASL
    description This update for curl fixes the following security issues : - CVE-2017-1000254: FTP PWD response parser out of bounds read (bsc#1061876) Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-11-30
    plugin id 104991
    published 2017-12-04
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=104991
    title SUSE SLES11 Security Update : curl (SUSE-SU-2017:3176-1)
  • NASL family Amazon Linux Local Security Checks
    NASL id ALA_ALAS-2017-919.NASL
    description FTP PWD response parser out of bounds read libcurl may read outside of a heap allocated buffer when doing FTP. When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. The simple fact that this has issue remained undiscovered for this long could suggest that malformed PWD responses are rare in benign servers. We are not aware of any exploit of this flaw. This bug was introduced in commit [415d2e7cb7](https://github.com/curl/curl/commit/415d2e7cb7), March 2005. In libcurl version 7.56.0, the parser always zero terminates the string but also rejects it if not terminated properly with a final double quote. (CVE-2017-1000254 )
    last seen 2019-02-21
    modified 2018-04-18
    plugin id 104393
    published 2017-11-06
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=104393
    title Amazon Linux AMI : curl (ALAS-2017-919)
  • NASL family Huawei Local Security Checks
    NASL id EULEROS_SA-2017-1287.NASL
    description According to the version of the curl packages installed, the EulerOS installation on the remote host is affected by the following vulnerability : - libcurl may read outside of a heap allocated buffer when doing FTP. When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. The simple fact that this has issue remained undiscovered for this long could suggest that malformed PWD responses are rare in benign servers. We are not aware of any exploit of this flaw. This bug was introduced in commit [415d2e7cb7](https://github.com/curl/curl/commit/415d2e 7cb7), March 2005. In libcurl version 7.56.0, the parser always zero terminates the string but also rejects it if not terminated properly with a final double quote.(CVE-2017-1000254) Note that Tenable Network Security has extracted the preceding description block directly from the EulerOS security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-11-14
    plugin id 104906
    published 2017-12-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=104906
    title EulerOS 2.0 SP1 : curl (EulerOS-SA-2017-1287)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2017-601B4C20A4.NASL
    description - fix out of bounds read in FTP PWD response parser (CVE-2017-1000254) Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-02-01
    plugin id 103895
    published 2017-10-18
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=103895
    title Fedora 26 : curl (2017-601b4c20a4)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2017-1200.NASL
    description This update for curl fixes the following issues : Security issues fixed : - CVE-2017-1000254: FTP PWD response parser out of bounds read (bsc#1061876) - CVE-2017-1000257: IMAP FETCH response out of bounds read (bsc#1063824) Bugs fixed : - Fixed error 'error:1408F10B:SSL routines' when connecting to ftps via proxy (bsc#1060653) This update was imported from the SUSE:SLE-12:Update update project.
    last seen 2019-02-21
    modified 2018-01-26
    plugin id 104236
    published 2017-10-30
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=104236
    title openSUSE Security Update : curl (openSUSE-2017-1200)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_SU-2017-2831-1.NASL
    description This update for curl fixes the following issues: Security issues fixed : - CVE-2017-1000254: FTP PWD response parser out of bounds read (bsc#1061876) - CVE-2017-1000257: IMAP FETCH response out of bounds read (bsc#1063824) Bugs fixed : - Fixed error 'error:1408F10B:SSL routines' when connecting to ftps via proxy (bsc#1060653) Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-11-30
    plugin id 104117
    published 2017-10-24
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=104117
    title SUSE SLED12 / SLES12 Security Update : curl (SUSE-SU-2017:2831-1)
  • NASL family MacOS X Local Security Checks
    NASL id MACOS_10_13_2.NASL
    description The remote host is running a version of Mac OS X that is 10.13.x prior to 10.13.2. It is, therefore, affected by multiple vulnerabilities in the following components : - apache - curl - Directory Utility - IOAcceleratorFamily - IOKit - Intel Graphics Driver - Kernel - Mail - Mail Drafts - OpenSSL - Screen Sharing Server Note that successful exploitation of the most serious issues can result in arbitrary code execution.
    last seen 2019-02-21
    modified 2018-07-14
    plugin id 105080
    published 2017-12-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=105080
    title macOS 10.13.x < 10.13.2 Multiple Vulnerabilities (Meltdown)
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DLA-1121.NASL
    description It was discovered that there was a out-of-bounds read vulnerability in curl, a command-line and library for transferring data over HTTP/FTP, etc. A malicious FTP server could abuse this to prevent curl-based clients from interacting with it. See for more details. For Debian 7 'Wheezy', this issue has been fixed in curl version 7.26.0-1+wheezy21. We recommend that you upgrade your curl packages. NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-18
    plugin id 103682
    published 2017-10-06
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=103682
    title Debian DLA-1121-1 : curl security update
  • NASL family PhotonOS Local Security Checks
    NASL id PHOTONOS_PHSA-2017-0045_CURL.NASL
    description An update of the curl package has been released.
    last seen 2019-02-08
    modified 2019-02-07
    plugin id 121761
    published 2019-02-07
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=121761
    title Photon OS 2.0: Curl PHSA-2017-0045
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201712-04.NASL
    description The remote host is affected by the vulnerability described in GLSA-201712-04 (cURL: Multiple vulnerabilities) Multiple vulnerabilities have been discovered in cURL. Please review the CVE identifiers referenced below for details. Impact : Remote attackers could cause a Denial of Service condition, disclose sensitive information or other unspecified impacts. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-01-26
    plugin id 105264
    published 2017-12-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=105264
    title GLSA-201712-04 : cURL: Multiple vulnerabilities
  • NASL family Amazon Linux Local Security Checks
    NASL id AL2_ALAS-2019-1162.NASL
    description libcurl is vulnerable to a heap buffer out-of-bounds read. The function handling incoming NTLM type-2 messages (`lib/vauth/ntlm.c:ntlm_decode_type2_target`) does not validate incoming data correctly and is subject to an integer overflow vulnerability. Using that overflow, a malicious or broken NTLM server could trick libcurl to accept a bad length + offset combination that would lead to a buffer read out-of-bounds.(CVE-2018-16890) The NTLM authentication feature in curl and libcurl before 7.57.0 on 32-bit platforms allows attackers to cause a denial of service (integer overflow and resultant buffer overflow, and application crash) or possibly have unspecified other impact via vectors involving long user and password fields.(CVE-2017-8816) curl and libcurl before 7.57.0 on 32-bit platforms allow attackers to cause a denial of service (out-of-bounds access and application crash) or possibly have unspecified other impact because too little memory is allocated for interfacing to an SSL library.(CVE-2017-8818) libcurl may read outside of a heap allocated buffer when doing FTP. When libcurl connects to an FTP server and successfully logs in (anonymous or not), it asks the server for the current directory with the `PWD` command. The server then responds with a 257 response containing the path, inside double quotes. The returned path name is then kept by libcurl for subsequent uses. Due to a flaw in the string parser for this directory name, a directory name passed like this but without a closing double quote would lead to libcurl not adding a trailing NUL byte to the buffer holding the name. When libcurl would then later access the string, it could read beyond the allocated heap buffer and crash or wrongly access data beyond the buffer, thinking it was part of the path. A malicious server could abuse this fact and effectively prevent libcurl-based clients to work with it - the PWD command is always issued on new FTP connections and the mistake has a high chance of causing a segfault. The simple fact that this has issue remained undiscovered for this long could suggest that malformed PWD responses are rare in benign servers. We are not aware of any exploit of this flaw. This bug was introduced in commit [415d2e7cb7](https://github.com/curl/curl/commit/415d2e7cb7), March 2005. In libcurl version 7.56.0, the parser always zero terminates the string but also rejects it if not terminated properly with a final double quote.(CVE-2017-1000254) Curl versions 7.14.1 through 7.61.1 are vulnerable to a heap-based buffer over-read in the tool_msgs.c:voutf() function that may result in information exposure and denial of service.(CVE-2018-16842) libcurl is vulnerable to a stack-based buffer overflow. The function creating an outgoing NTLM type-3 header (`lib/vauth/ntlm.c:Curl_auth_create_ntlm_type3_message()`), generates the request HTTP header contents based on previously received data. The check that exists to prevent the local buffer from getting overflowed is implemented wrongly (using unsigned math) and as such it does not prevent the overflow from happening. This output data can grow larger than the local buffer if very large 'nt response' data is extracted from a previous NTLMv2 header provided by the malicious or broken HTTP server. Such a 'large value' needs to be around 1000 bytes or more. The actual payload data copied to the target buffer comes from the NTLMv2 type-2 response header.(CVE-2019-3822) libcurl is vulnerable to a heap out-of-bounds read in the code handling the end-of-response for SMTP. If the buffer passed to `smtp_endofresp()` isn't NUL terminated and contains no character ending the parsed number, and `len` is set to 5, then the `strtol()` call reads beyond the allocated buffer. The read contents will not be returned to the caller.(CVE-2019-3823) The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and application crash) or possibly have unspecified other impact via a string that ends with an '[' character.(CVE-2017-8817) set_file_metadata in xattr.c in GNU Wget before 1.20.1 stores a file's origin URL in the user.xdg.origin.url metadata attribute of the extended attributes of the downloaded file, which allows local users to obtain sensitive information (e.g., credentials contained in the URL) by reading this attribute, as demonstrated by getfattr. This also applies to Referer information in the user.xdg.referrer.url metadata attribute. According to 2016-07-22 in the Wget ChangeLog, user.xdg.origin.url was partially based on the behavior of fwrite_xattr in tool_xattr.c in curl.(CVE-2018-20483) A buffer overrun flaw was found in the IMAP handler of libcurl. By tricking an unsuspecting user into connecting to a malicious IMAP server, an attacker could exploit this flaw to potentially cause information disclosure or crash the application.(CVE-2017-1000257) A heap use-after-free flaw was found in curl versions from 7.59.0 through 7.61.1 in the code related to closing an easy handle. When closing and cleaning up an 'easy' handle in the `Curl_close()` function, the library code first frees a struct (without nulling the pointer) and might then subsequently erroneously write to a struct field within that already freed struct.(CVE-2018-16840) Curl versions 7.33.0 through 7.61.1 are vulnerable to a buffer overrun in the SASL authentication code that may lead to denial of service.(CVE-2018-16839)
    last seen 2019-02-21
    modified 2019-02-19
    plugin id 122260
    published 2019-02-19
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=122260
    title Amazon Linux 2 : curl (ALAS-2019-1162)
  • NASL family Ubuntu Local Security Checks
    NASL id UBUNTU_USN-3441-1.NASL
    description Daniel Stenberg discovered that curl incorrectly handled large floating point output. A remote attacker could use this issue to cause curl to crash, resulting in a denial of service, or possibly execute arbitrary code. This issue only affected Ubuntu 14.04 LTS and Ubuntu 16.04 LTS. (CVE-2016-9586) Even Rouault discovered that curl incorrectly handled large file names when doing TFTP transfers. A remote attacker could use this issue to cause curl to crash, resulting in a denial of service, or possibly obtain sensitive memory contents. (CVE-2017-1000100) Brian Carpenter and Yongji Ouyang discovered that curl incorrectly handled numerical range globbing. A remote attacker could use this issue to cause curl to crash, resulting in a denial of service, or possibly obtain sensitive memory contents. (CVE-2017-1000101) Max Dymond discovered that curl incorrectly handled FTP PWD responses. A remote attacker could use this issue to cause curl to crash, resulting in a denial of service. (CVE-2017-1000254) Brian Carpenter discovered that curl incorrectly handled the --write-out command line option. A local attacker could possibly use this issue to obtain sensitive memory contents. (CVE-2017-7407). Note that Tenable Network Security has extracted the preceding description block directly from the Ubuntu security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2018-12-01
    plugin id 103773
    published 2017-10-11
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=103773
    title Ubuntu 14.04 LTS / 16.04 LTS / 17.04 : curl vulnerabilities (USN-3441-1)
redhat via4
advisories
  • rhsa
    id RHSA-2018:2486
  • rhsa
    id RHSA-2018:3558
refmap via4
bid 101115
confirm
debian DSA-3992
gentoo GLSA-201712-04
sectrack 1039509
Last major update 06-10-2017 - 09:29
Published 06-10-2017 - 09:29
Last modified 13-11-2018 - 06:29
Back to Top