CVE-2017-1000254
Reported by mitre · Published October 6, 2017
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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| libcurl-gnutls | Arch Linux | 7.56.0-1 |
| curl | Alpine | 7.56.0-r0, 7.55.0-r1 |
| lib32-libcurl-compat | Arch Linux | 7.56.0-1 |
| libcurl-compat | Arch Linux | 7.56.0-1 |
| libcurl-devel | Amazon Linux | 7.61.1-9.amzn2.0.1 |
Affected products
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
| arch | libcurl-gnutls | 0 |
| alpine | curl | 0, 0 |
| arch | lib32-libcurl-compat | 0 |
| arch | libcurl-compat | 0 |
| amazon:2 | libcurl-devel | 0 |
| n/a | n/a | * |
| arch | lib32-curl | 0 |
| amazon:2 | curl | 0 |
| amazon:2 | libcurl | 0 |
| arch | curl | 0 |
| arch | lib32-libcurl-gnutls | 0 |
Timeline
- Oct 6, 2017 CVE Published
- Apr 14, 2021 EPSS Score (30 in total, the first dated here)
- Mar 5, 2026 Distribution Patch (7 in total, the first dated here)
- Mar 5, 2026 Security Advisory (7 in total, the first dated here)
- Oct 5, 2026 Coalition ESS Score
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2017-1000254
vulnetix vdb fixes CVE-2017-1000254
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-1000254/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart
References
- GLSA-201712-04 vendor-advisoryx_refsource_GENTOO
- RHSA-2018:3558 vendor-advisoryx_refsource_REDHAT
- x_refsource_CONFIRM
- 1039509 vdb-entryx_refsource_SECTRACK
- x_refsource_CONFIRM
- x_refsource_CONFIRM
- RHSA-2018:2486 vendor-advisoryx_refsource_REDHAT
- DSA-3992 vendor-advisoryx_refsource_DEBIAN
- 101115 vdb-entryx_refsource_BID
- [bookkeeper-issues] 20210628 [GitHub] [bookkeeper] padma81 opened a new issue #2746: Security Vulnerabilities in CentOS 7 image, Upgrade image to CentOS 8 mailing-listx_refsource_MLIST
- [bookkeeper-issues] 20210629 [GitHub] [bookkeeper] padma81 opened a new issue #2746: Security Vulnerabilities in CentOS 7 image, Upgrade image to CentOS 8 mailing-listx_refsource_MLIST