This is a potential security issue, you are being redirected to https://nvd.nist.gov
Search & Statistics
CVSS V3 Calculator
CVSS V2 Calculator
Checklist (NCP) Repository
SCAP Validated Tools
This vulnerability has been modified since it was last analyzed by the NVD. It is awaiting reanalysis which may result in further changes to the information provided.
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.
View Analysis Description
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because
they may have information that would be of interest to you. No inferences should be drawn on account of other sites
being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose.
NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further,
NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about
this page to firstname.lastname@example.org.
https://access.redhat.com/errata/RHSA-2018:3558 [No Types Assigned]
https://access.redhat.com/errata/RHSA-2018:2486 [No Types Assigned]
https://support.apple.com/HT208331 [No Types Assigned]
https://security.gentoo.org/glsa/201712-04 [No Types Assigned]
http://www.debian.org/security/2017/dsa-3992 [No Types Assigned]
http://www.securityfocus.com/bid/101115 No Types Assigned
http://www.securityfocus.com/bid/101115 Third Party Advisory, VDB Entry
http://www.securitytracker.com/id/1039509 No Types Assigned
http://www.securitytracker.com/id/1039509 Third Party Advisory, VDB Entry
https://curl.haxx.se/673d0cd8.patch No Types Assigned
https://curl.haxx.se/673d0cd8.patch Patch, Vendor Advisory
https://curl.haxx.se/docs/adv_20171004.html No Types Assigned
https://curl.haxx.se/docs/adv_20171004.html Patch, Vendor Advisory
https://curl.haxx.se/docs/adv_20171004.html [No Types Assigned]
http://www.securityfocus.com/bid/101115 [No Types Assigned]
http://www.securitytracker.com/id/1039509 [No Types Assigned]