{"id":"CVE-2017-1000254","aliases":["ALPINE-CVE-2017-1000254","BELL-CVE-2017-1000254","CURL-CVE-2017-1000254","DEBIAN-CVE-2017-1000254","DLA-1121-1","DSA-3992-1","EUVD-2017-1515","GHSA-499v-2pwm-c696","MGASA-2018-0053","MGASA-2018-0054","RHSA-2018:3558","SUSE-SU-2017:2789-1","SUSE-SU-2017:2831-1","SUSE-SU-2017:3176-1","SUSE-SU-2018:0214-1","UBUNTU-CVE-2017-1000254","USN-3441-1","openSUSE-SU-2024:10582-1"],"status":"published","title":"libcurl may read outside of a heap allocated buffer when doing FTP. When libcurl connects to an...","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.","severity":{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"primary","from":"nvd"},"epss":{"day":"2026-11-09","score":0.08139,"percentile":0.94885,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-119"],"published":"2017-10-04T00:00:00Z","modified":"2026-10-25T01:04:51Z","fixes":[{"ecosystem":"Alpine:v3.3","package":"curl","fixed_in":["7.55.0-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.4","package":"curl","fixed_in":["7.55.0-r1"],"sources":["osv"]},{"ecosystem":"Alpine:v3.5","package":"curl","fixed_in":["7.56.0-r0"],"sources":["osv"]},{"ecosystem":"Alpine:v3.6","package":"curl","fixed_in":["7.56.0-r0"],"sources":["osv"]},{"ecosystem":"Debian:12","package":"curl","fixed_in":["7.56.1-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"curl","fixed_in":["7.56.1-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"curl","fixed_in":["7.56.1-1"],"sources":["osv"]},{"ecosystem":"Debian:7","package":"curl","fixed_in":["7.26.0-1+wheezy21"],"sources":["osv"]},{"ecosystem":"SUSE:Studio Onsite 1.3","package":"curl","fixed_in":["7.19.7-1.20.53.6.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Software Development Kit 11 SP4","package":"curl","fixed_in":["7.19.7-1.70.8.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server 11-SECURITY","package":"curl-openssl1","fixed_in":["7.19.7-1.70.8.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server 11 SP4","package":"curl","fixed_in":["7.19.7-1.70.8.1"],"sources":["osv"]},{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 11 SP4","package":"curl","fixed_in":["7.19.7-1.70.8.1"],"sources":["osv"]},{"ecosystem":"Ubuntu:14.04:LTS","package":"curl","fixed_in":["7.35.0-1ubuntu2.11"],"sources":["osv"]},{"ecosystem":"Ubuntu:16.04:LTS","package":"curl","fixed_in":["7.47.0-1ubuntu2.3"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Alpine:v3.3","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.55.0-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.4","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.55.0-r1"}]}]},{"source":"osv","ecosystem":"Alpine:v3.5","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.56.0-r0"}]}]},{"source":"osv","ecosystem":"Alpine:v3.6","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.56.0-r0"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.56.1-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.56.1-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.56.1-1"}]}]},{"source":"osv","ecosystem":"Debian:7","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.26.0-1+wheezy21"}]}],"versions":["7.26.0-1+wheezy10","7.26.0-1+wheezy11","7.26.0-1+wheezy12","7.26.0-1+wheezy13","7.26.0-1+wheezy14","7.26.0-1+wheezy15","7.26.0-1+wheezy16","7.26.0-1+wheezy17","7.26.0-1+wheezy18","7.26.0-1+wheezy19","7.26.0-1+wheezy2","7.26.0-1+wheezy20","7.26.0-1+wheezy3","7.26.0-1+wheezy4","7.26.0-1+wheezy5","7.26.0-1+wheezy6","7.26.0-1+wheezy7","7.26.0-1+wheezy8","7.26.0-1+wheezy9"]},{"source":"osv","ecosystem":"Debian:8","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.38.0-4+deb8u6"}]}],"versions":["7.38.0-4","7.38.0-4+deb8u1","7.38.0-4+deb8u2","7.38.0-4+deb8u3","7.38.0-4+deb8u4","7.38.0-4+deb8u5"],"bundled":3},{"source":"osv","ecosystem":"Debian:9","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.52.1-5+deb9u1"}]}],"versions":["7.52.1-5"],"bundled":3},{"source":"osv","ecosystem":"Mageia:5","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.40.0-3.14.mga5"}]}],"bundled":18},{"source":"osv","ecosystem":"Mageia:6","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.54.1-2.4.mga6"}]}],"bundled":4},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.61.1-1.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-curl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.61.1-1.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-httpd","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-httpd-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-httpd-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-httpd-manual","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-httpd-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-libcurl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.61.1-1.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-libcurl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.61.1-1.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-libnghttp2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.7.1-7.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-libnghttp2-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.7.1-7.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-mod_ldap","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-mod_proxy_html","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.4.34-7.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-mod_session","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-mod_ssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.4.34-7.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-nghttp2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.7.1-7.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el6","package":"httpd24-nghttp2-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.7.1-7.el6"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.61.1-1.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-curl-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.61.1-1.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-httpd","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-httpd-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-httpd-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-httpd-manual","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-httpd-tools","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-libcurl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.61.1-1.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-libcurl-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:7.61.1-1.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-libnghttp2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.7.1-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-libnghttp2-devel","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.7.1-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-mod_ldap","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-mod_md","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-mod_proxy_html","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.4.34-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-mod_session","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:2.4.34-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-mod_ssl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1:2.4.34-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-nghttp2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.7.1-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"Red Hat:rhel_software_collections:3::el7","package":"httpd24-nghttp2-debuginfo","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.7.1-7.el7"}]}],"bundled":38},{"source":"osv","ecosystem":"SUSE:Studio Onsite 1.3","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.19.7-1.20.53.6.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP2","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.37.0-37.8.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Desktop 12 SP3","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.37.0-37.8.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.37.0-37.8.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP2","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.37.0-37.8.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP3","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.37.0-37.8.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP2","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.37.0-37.8.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP2","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.37.0-37.8.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 12 SP3","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.37.0-37.8.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP3","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.37.0-37.8.1"}]}],"bundled":2},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Software Development Kit 11 SP4","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.19.7-1.70.8.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11-SECURITY","package":"curl-openssl1","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.19.7-1.70.8.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server 11 SP4","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.19.7-1.70.8.1"}]}]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 11 SP4","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.19.7-1.70.8.1"}]}]},{"source":"osv","ecosystem":"SUSE:Studio Onsite 1.3","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.19.7-1.20.53.13.1"}]}],"bundled":2},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.35.0-1ubuntu2.11"}]}],"versions":["7.32.0-1ubuntu1","7.33.0-1ubuntu1","7.34.0-1ubuntu1","7.35.0-1ubuntu1","7.35.0-1ubuntu2","7.35.0-1ubuntu2.1","7.35.0-1ubuntu2.2","7.35.0-1ubuntu2.3","7.35.0-1ubuntu2.5","7.35.0-1ubuntu2.6","7.35.0-1ubuntu2.7","7.35.0-1ubuntu2.8","7.35.0-1ubuntu2.9","7.35.0-1ubuntu2.10"]},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.47.0-1ubuntu2.3"}]}],"versions":["7.43.0-1ubuntu2","7.45.0-1ubuntu1","7.46.0-1ubuntu1","7.47.0-1ubuntu1","7.47.0-1ubuntu2","7.47.0-1ubuntu2.1","7.47.0-1ubuntu2.2"]},{"source":"osv","ecosystem":"Ubuntu:14.04:LTS","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.35.0-1ubuntu2.11"}]}],"versions":["7.32.0-1ubuntu1","7.33.0-1ubuntu1","7.34.0-1ubuntu1","7.35.0-1ubuntu1","7.35.0-1ubuntu2","7.35.0-1ubuntu2.1","7.35.0-1ubuntu2.2","7.35.0-1ubuntu2.3","7.35.0-1ubuntu2.5","7.35.0-1ubuntu2.6","7.35.0-1ubuntu2.7","7.35.0-1ubuntu2.8","7.35.0-1ubuntu2.9","7.35.0-1ubuntu2.10"],"bundled":5},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.47.0-1ubuntu2.3"}]}],"versions":["7.43.0-1ubuntu2","7.45.0-1ubuntu1","7.46.0-1ubuntu1","7.47.0-1ubuntu1","7.47.0-1ubuntu2","7.47.0-1ubuntu2.1","7.47.0-1ubuntu2.2"],"bundled":5},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"curl","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.79.1-1.1"}]}],"bundled":48}],"products":[{"vendor":"haxx","product":"libcurl"}],"references":[{"url":"https://security.gentoo.org/glsa/201712-04","tags":["vendor-advisory","x_refsource_GENTOO","x_transferred","advisory"]},{"url":"https://access.redhat.com/errata/RHSA-2018:3558","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","advisory"]},{"url":"https://support.apple.com/HT208331","tags":["x_refsource_CONFIRM","x_transferred","web"]},{"url":"http://www.securitytracker.com/id/1039509","tags":["vdb-entry","x_refsource_SECTRACK","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"https://curl.haxx.se/673d0cd8.patch","tags":["x_refsource_CONFIRM","x_transferred","Patch","Vendor Advisory","fix"]},{"url":"https://curl.haxx.se/docs/adv_20171004.html","tags":["x_refsource_CONFIRM","x_transferred","Patch","Vendor Advisory","fix","web","article","report"]},{"url":"https://access.redhat.com/errata/RHSA-2018:2486","tags":["vendor-advisory","x_refsource_REDHAT","x_transferred","advisory"]},{"url":"http://www.debian.org/security/2017/dsa-3992","tags":["vendor-advisory","x_refsource_DEBIAN","x_transferred","advisory"]},{"url":"http://www.securityfocus.com/bid/101115","tags":["vdb-entry","x_refsource_BID","x_transferred","Third Party Advisory","VDB Entry","advisory"]},{"url":"https://lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%3Cissues.bookkeeper.apache.org%3E","tags":["mailing-list","x_refsource_MLIST","x_transferred","web"]},{"url":"https://lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%3Cissues.bookkeeper.apache.org%3E","tags":["mailing-list","x_refsource_MLIST","x_transferred","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-1000254","tags":["advisory"]},{"url":"https://lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b@%3Cissues.bookkeeper.apache.org%3E"},{"url":"https://lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4@%3Cissues.bookkeeper.apache.org%3E"},{"url":"https://github.com/advisories/GHSA-499v-2pwm-c696"},{"url":"https://security.alpinelinux.org/vuln/CVE-2017-1000254","tags":["advisory"]},{"url":"https://docs.bell-sw.com/security/cves/CVE-2017-1000254","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2017-1000254","tags":["advisory"]},{"url":"https://advisories.mageia.org/MGASA-2018-0053.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=19700","tags":["report"]},{"url":"https://curl.haxx.se/docs/adv_20161102A.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20161102B.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20161102C.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20161102D.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20161102E.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20161102F.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20161102G.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20161102H.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20161102I.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20161102J.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20161221A.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20170403.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20170809A.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20170809B.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_20171023.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_2017-12e7.html","tags":["web","article"]},{"url":"https://curl.haxx.se/docs/adv_2017-ae72.html","tags":["web","article"]},{"url":"https://advisories.mageia.org/MGASA-2018-0054.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=21819","tags":["report"]},{"url":"https://access.redhat.com/security/updates/classification/#moderate","tags":["article"]},{"url":"https://access.redhat.com/documentation/en-us/red_hat_software_collections/3/html/3.2_release_notes/chap-rhscl#sect-RHSCL-Changes-httpd","tags":["article"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1362183","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1362190","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1362199","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1373229","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1375906","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1388370","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1388371","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1388377","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1388378","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1388379","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1388382","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1388385","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1388386","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1388388","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1388390","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1388392","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1406712","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1439190","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1478309","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1478310","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1495541","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1503705","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1515757","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1515760","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1518737","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1537125","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1540167","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1552628","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1552631","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1553398","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1558450","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1560395","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1560399","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1560599","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1560614","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1560634","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1560643","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1575536","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1605048","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1622707","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1628389","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1633260","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1633399","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1634830","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1640722","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1646937","tags":["report"]},{"url":"https://bugzilla.redhat.com/show_bug.cgi?id=1648928","tags":["report"]},{"url":"https://security.access.redhat.com/data/csaf/v2/advisories/2018/rhsa-2018_3558.json","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-5419","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-5419","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-5419","tags":["advisory"]},{"url":"https://curl.haxx.se/docs/adv_20160803A.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-5420","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-5420","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-5420","tags":["advisory"]},{"url":"https://curl.haxx.se/docs/adv_20160803B.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-5421","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-5421","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-5421","tags":["advisory"]},{"url":"https://curl.haxx.se/docs/adv_20160803C.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-7141","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-7141","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-7141","tags":["advisory"]},{"url":"https://curl.haxx.se/docs/adv_20160907.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-7167","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-7167","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-7167","tags":["advisory"]},{"url":"https://curl.haxx.se/docs/adv_20160914.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-8615","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-8615","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-8615","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-8616","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-8616","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-8616","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-8617","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-8617","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-8617","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-8618","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-8618","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-8618","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-8619","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-8619","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-8619","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-8620","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-8620","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-8620","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-8621","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-8621","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-8621","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-8622","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-8622","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-8622","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-8623","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-8623","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-8623","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-8624","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-8624","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-8624","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-8625","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-8625","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-8625","tags":["advisory"]},{"url":"https://curl.haxx.se/docs/adv_20161102K.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2016-9586","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2016-9586","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2016-9586","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-7407","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-7407","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-7407","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-8816","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-8816","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-8816","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-8817","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-8817","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-8817","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-15710","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-15710","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-15710","tags":["advisory"]},{"url":"https://httpd.apache.org/security/vulnerabilities_24.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-15715","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-15715","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-15715","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-1000100","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-1000100","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-1000100","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-1000101","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-1000101","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-1000101","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-1000254","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-1000254","tags":["advisory","report"]},{"url":"https://access.redhat.com/security/cve/CVE-2017-1000257","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2017-1000257","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2017-1000257","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-1283","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-1283","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-1283","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-1301","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-1301","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-1301","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-1303","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-1303","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-1303","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-1312","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-1312","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-1312","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-1333","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-1333","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-1333","tags":["advisory"]},{"url":"https://httpd.apache.org/security/vulnerabilities_24.html#CVE-2018-1333","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-11763","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-11763","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-11763","tags":["advisory"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-14618","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-14618","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-14618","tags":["advisory"]},{"url":"https://curl.haxx.se/docs/CVE-2018-14618.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-1000007","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-1000007","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-1000007","tags":["advisory"]},{"url":"https://curl.haxx.se/docs/adv_2018-b3bf.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-1000120","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-1000120","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-1000120","tags":["advisory"]},{"url":"https://curl.haxx.se/docs/adv_2018-9cd6.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-1000121","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-1000121","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-1000121","tags":["advisory"]},{"url":"https://curl.haxx.se/docs/adv_2018-97a2.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-1000122","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-1000122","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-1000122","tags":["advisory"]},{"url":"https://curl.haxx.se/docs/adv_2018-b047.html","tags":["article"]},{"url":"https://access.redhat.com/security/cve/CVE-2018-1000301","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2018-1000301","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2018-1000301","tags":["advisory"]},{"url":"https://curl.haxx.se/docs/adv_2018-b138.html","tags":["article"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20172789-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1061876","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2017-1000254","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20172831-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1060653","tags":["report"]},{"url":"https://bugzilla.suse.com/1063824","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2017-1000257","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2017/suse-su-20173176-1/","tags":["advisory"]},{"url":"https://www.suse.com/support/update/announcement/2018/suse-su-20180214-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1027712","tags":["report"]},{"url":"https://bugzilla.suse.com/1077001","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2018-1000007","tags":["web"]},{"url":"https://ubuntu.com/security/CVE-2017-1000254","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-3441-1","tags":["advisory"]},{"url":"https://ubuntu.com/security/notices/USN-3441-2","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2016-9586","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-7407","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-1000100","tags":["report"]},{"url":"https://ubuntu.com/security/CVE-2017-1000101","tags":["report"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2006-1061","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9586","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2016-9594","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-1000099","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-1000100","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-1000101","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-2629","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-7468","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8816","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8817","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-8818","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2017-9502","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-0500","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-1000005","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-1000120","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-1000122","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-1000300","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-1000301","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-14618","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16839","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16840","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16842","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2018-16890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-15601","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-3822","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-3823","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-5435","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-5436","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-5481","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2019-5482","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8169","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8231","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8284","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8285","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2020-8286","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22297","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22298","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22876","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22890","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22898","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22901","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22922","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22924","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22945","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22946","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2021-22947","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2017-1000254","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.","status":"published","published":"2017-10-06T13:00:00Z","modified":"2024-08-05T22:00:39.675Z","updated_at":"2026-11-02T14:33:21.142987Z"}],"euvd":[{"id":"EUVD-2017-1515","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.","status":"published","published":"2017-10-06T13:00:00Z","modified":"2024-08-05T22:00:39Z","updated_at":"2026-11-03T02:23:03.593375Z"}],"ghsa":[{"id":"GHSA-499v-2pwm-c696","title":"libcurl may read outside of a heap allocated buffer when doing FTP. When libcurl connects to an...","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.","status":"published","published":"2022-05-13T01:09:02Z","modified":"2025-04-20T03:47:30Z","cvss":[{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"cwes":["CWE-119"],"updated_at":"2026-11-02T15:01:53.867735Z"}],"nvd":[{"id":"CVE-2017-1000254","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.","status":"published","published":"2017-10-06T13:29:00.207Z","modified":"2026-06-17T00:58:59.98Z","cvss":[{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high","assessor":"primary"},{"version":"2.0","score":5,"vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","level":"medium","assessor":"primary"}],"cwes":["CWE-119"],"updated_at":"2026-11-02T14:04:01.734197Z"}],"osv":[{"id":"ALPINE-CVE-2017-1000254","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.","status":"published","published":"2017-10-06T13:29:00.207Z","modified":"2026-06-15T18:23:54.930734942Z","cvss":[{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:27:46.716249Z"},{"id":"BELL-CVE-2017-1000254","title":"CVE-2017-1000254 does not affect BellSoft software","status":"withdrawn","published":"2017-10-06T13:29:00Z","modified":"2026-01-26T09:47:23.143846Z","cvss":[{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:28:14.137943Z"},{"id":"CVE-2017-1000254","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.","status":"published","published":"2017-10-06T13:29:00.207Z","modified":"2026-10-24T10:30:48.002685414Z","cvss":[{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:44:03.851821Z"},{"id":"DEBIAN-CVE-2017-1000254","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.","status":"published","published":"2017-10-06T13:29:00.207Z","modified":"2026-09-01T20:03:40.478784906Z","cvss":[{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:45:28.207321Z"},{"id":"RHSA-2018:3558","title":"Red Hat Security Advisory: httpd24 security, bug fix, and enhancement update","status":"published","published":"2024-09-13T16:54:33Z","modified":"2026-09-21T10:02:03Z","cvss":[{"version":"3.1","score":8.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","level":"high"}],"updated_at":"2026-11-02T15:53:05.383061Z"},{"id":"UBUNTU-CVE-2017-1000254","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.","status":"published","published":"2017-10-04T00:00:00Z","modified":"2026-04-22T11:09:30.122669Z","cvss":[{"version":"3.0","score":7.5,"vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","level":"high"}],"updated_at":"2026-11-02T15:54:13.729565Z"},{"id":"CURL-CVE-2017-1000254","title":"FTP PWD response parser out of bounds read","description":"libcurl may read outside of a heap allocated buffer when doing FTP.\n\nWhen libcurl connects to an FTP server and successfully logs in (anonymous or\nnot), it asks the server for the current directory with the `PWD` command. The\nserver then responds with a 257 response containing the path, inside double\nquotes. The returned path name is then kept by libcurl for subsequent uses.\n\nDue to a flaw in the string parser for this directory name, a directory name\npassed like this but without a closing double quote would lead to libcurl not\nadding a trailing null byte to the buffer holding the name. When libcurl would\nthen later access the string, it could read beyond the allocated heap buffer\nand crash or wrongly access data beyond the buffer, thinking it was part of\nthe path.\n\nA malicious server could abuse this fact and effectively prevent libcurl-based\nclients to work with it - the PWD command is always issued on new FTP\nconnections and the mistake has a high chance of causing a segfault.\n\nThe simple fact that this issue has remained undiscovered for this long could\nsuggest that malformed PWD responses are rare in benign servers.","status":"published","published":"2017-10-04T08:00:00Z","modified":"2026-10-25T01:04:51.251723371Z","updated_at":"2026-11-02T15:43:55.669514Z"},{"id":"DLA-1121-1","title":"curl - security update","status":"published","published":"2017-10-05T00:00:00Z","modified":"2026-03-09T01:01:53.031536Z","updated_at":"2026-11-02T15:46:09.336894Z"},{"id":"DSA-3992-1","title":"curl - security update","status":"published","published":"2017-10-06T00:00:00Z","modified":"2026-03-09T01:21:20.108445Z","updated_at":"2026-11-02T15:46:16.523846Z"},{"id":"MGASA-2018-0053","title":"Updated curl packages fix security vulnerability","description":"If cookie state is written into a cookie jar file that is later read back and\nused for subsequent requests, a malicious HTTP server can inject new cookies\nfor arbitrary domains into said cookie jar. The issue pertains to the function\nthat loads cookies into memory, which reads the specified file into a\nfixed-size buffer in a line-by-line manner using the fgets() function. If an\ninvocation of fgets() cannot read the whole line into the destination buffer\ndue to it being too small, it truncates the output. This way, a very long\ncookie (name + value) sent by a malicious server would be stored in the file\nand subsequently that cookie could be read partially and crafted correctly, it\ncould be treated as a different cookie for another server (CVE-2016-8615).\n\nWhen re-using a connection, curl was doing case insensitive comparisons of\nuser name and password with the existing connections. This means that if an\nunused connection with proper credentials exists for a protocol that has\nconnection-scoped credentials, an attacker can cause that connection to be\nreused if s/he knows the case-insensitive version of the correct password\n(CVE-2016-8616).\n\nIn libcurl's base64 encode function, the output buffer is allocated without\nany checks on a variable used to determine its size. On systems with 32-bit\naddresses in userspace, the multiplication in the expression wraps around if\nthe size is too large. If this happens, an undersized output buffer will be\nallocated, but the full result will be written, thus causing the memory behind\nthe output buffer to be overwritten. If a username is set directly via\nCURLOPT_USERNAME (or curl's -u, --user option), this vulnerability can be\ntriggered. The name has to be at least 512MB big in a 32bit system. Systems\nwith 64 bit versions of the size_t type are not affected by this issue\n(CVE-2016-8617).\n\nThe libcurl API function called curl_maprintf() can be tricked into doing a\ndouble-free due to an unsafe size_t multiplication, on systems using 32 bit\nsize_t variables. The function is also used internallty in numerous\nsituations. The function doubles an allocated memory area with realloc() and\nallows the size to wrap and become zero and when doing so realloc() returns\nNULL and frees the memory - in contrary to normal realloc() fails where it\nonly returns NULL - causing libcurl to free the memory again in the error\npath. Systems with 64 bit versions of the size_t type are not affected by this\nissue. This behavior is triggable using the publicly exposed function\n(CVE-2016-8618).\n\nIn curl's implementation of the Kerberos authentication mechanism, the\nfunction read_data() in security.c is used to fill the necessary krb5\nstructures. When reading one of the length fields from the socket, it fails to\nensure that the length parameter passed to realloc() is not set to 0. This\nwould lead to realloc() getting called with a zero size and when doing so\nrealloc() returns NULL and frees the memory - in contrary to normal realloc()\nfails where it only returns NULL - causing libcurl to free the memory again in\nthe error path. This flaw could be triggered by a malicious or just otherwise\nill-behaving server (CVE-2016-8619).\n\nThe curl tool's \"globbing\" feature allows a user to specify a numerical range\nthrough which curl will iterate. The curl code for parsing the second unsigned\nnumber did not check for a leading minus character, which allowed a user to\nspecify [1--1] with no complaints and have the latter -1 number get turned\ninto the largest unsigned long value the system can handle. This would\nultimately cause curl to write outside the dedicated malloced buffer after no\nless than 100,000 iterations, since it would have room for 5 digits but not 6.\nWhen the range is specified with letters, and the ending letter is left out\n[L-], the code would still advance its read pointer 5 bytes even if the string\nwas just 4 bytes and end up reading outside the given buffer. This flaw exists\nonly in the curl tool, not in the libcurl library (CVE-2016-8620).\n\nThe curl_getdate date parser function would parse either a string with HH:MM\nor HH:MM:SS. If instead the piece of time that was sent in had the final digit\ncut off, thus ending with a single-digit, the date parser code would advance\nits read pointer one byte too much and end up reading out of bounds\n(CVE-2016-8621).\n\nThe URL percent-encoding decode function in libcurl is called\ncurl_easy_unescape. Internally, even if this function would be made to\nallocate a unscape destination buffer larger than 2GB, it would return that\nnew length in a signed 32 bit integer variable, thus the length would get\neither just truncated or both truncated and turned negative. That could then\nlead to libcurl writing outside of its heap based buffer. This can be\ntriggered by a user on a 64bit system if the user can send in a custom (very\nlarge) URL to a libcurl using program (CVE-2016-8622).\n\nlibcurl explicitly allows users to share cookies between multiple easy handles\nthat are concurrently employed by different threads. When cookies to be sent\nto a server are collected, the matching function collects all cookies to send\nand the cookie lock is released immediately afterwards. That funcion however\nonly returns a list with references back to the original strings for name,\nvalue, path and so on. Therefore, if another thread quickly takes the lock and\nfrees one of the original cookie structs together with its strings, a\nuse-after-free can occur and lead to information disclosure. Another thread\ncan also replace the contents of the cookies from separate HTTP responses or\nAPI calls (CVE-2016-8623).\n\ncurl doesn't parse the authority component of the URL correctly when the host\nname part ends with a '#' character, and could instead be tricked into\nconnecting to a different host. This may have security implications if you for\nexample use a URL parser that follows the RFC to check for allowed domains\nbefore using curl to request them (CVE-2016-8624).\n\nlibcurl's implementation of the printf() functions triggers a buffer overflow\nwhen doing a large floating point output. The bug occurs when the conversion\noutputs more than 255 bytes. The flaw happens because the floating point\nconversion is using system functions without the correct boundary checks\n(CVE-2016-9586).\n\nThere were two bugs in curl's parser for the command line option --write-out\n(or -w for short) that would skip the end of string zero byte if the string\nended in a % (percent) or \\ (backslash), and it would read beyond that buffer\nin the heap memory and it could then potentially output pieces of that memory\nto the terminal or the target file etc (CVE-2017-7407).\n\nWhen doing a TFTP transfer and curl/libcurl is given a URL that contains a very\nlong file name (longer than about 515 bytes), the file name is truncated to fit\nwithin the buffer boundaries, but the buffer size is still wrongly updated to\nuse the untruncated length. This too large value is then used in the sendto()\ncall, making curl attempt to send more data than what is actually put into the\nbuffer. The sendto() function will then read beyond the end of the heap based\nbuffer. A malicious HTTP(S) server could redirect a vulnerable libcurl-using\nclient to a crafted TFTP URL (if the client hasn't restricted which protocols\nit allows redirects to) and trick it to send private memory contents to a\nremote server over UDP. Limit curl's redirect protocols with --proto-redir and\nlibcurl's with CURLOPT_REDIR_PROTOCOLS (CVE-2017-1000100).\n\ncurl supports \"globbing\" of URLs, in which a user can pass a numerical range to\nhave the tool iterate over those numbers to do a sequence of transfers. In the\nglobbing function that parses the numerical range, there was an omission that\nmade curl read a byte beyond the end of the URL if given a carefully crafted,\nor just wrongly written, URL. The URL is stored in a heap based buffer, so it\ncould then be made to wrongly read something else instead of crashing\n(CVE-2017-1000101).\n\nlibcurl contains a buffer overrun flaw in the NTLM authentication code\n(CVE-2017-8816).\n\nlibcurl contains a read out of bounds flaw in the FTP wildcard function\n(CVE-2017-8817).\n\nlibcurl may read outside of a heap allocated buffer when doing FTP\n(CVE-2017-1000254).\n\nlibcurl contains a buffer overrun flaw in the IMAP handler\n(CVE-2017-1000257).\n","status":"published","published":"2018-01-03T16:40:26Z","modified":"2026-04-16T06:22:26.528381271Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"MGASA-2018-0054","title":"Updated curl packages fix security vulnerability","description":"libcurl contains a buffer overrun flaw in the NTLM authentication code\n(CVE-2017-8816).\n\nlibcurl contains a read out of bounds flaw in the FTP wildcard function\n(CVE-2017-8817).\n\nlibcurl may read outside of a heap allocated buffer when doing FTP\n(CVE-2017-1000254).\n\nlibcurl contains a buffer overrun flaw in the IMAP handler\n(CVE-2017-1000257).\n","status":"published","published":"2018-01-03T16:40:26Z","modified":"2026-04-16T06:23:39.731346652Z","updated_at":"2026-11-02T15:49:40.442238Z"},{"id":"openSUSE-SU-2024:10582-1","title":"curl-7.79.1-1.1 on GA media","description":"These are all security issues fixed in the curl-7.79.1-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2024-06-15T00:00:00Z","modified":"2026-02-04T04:40:36.472951Z","updated_at":"2026-11-02T16:58:34.487567Z"},{"id":"SUSE-SU-2017:2789-1","title":"Security update for curl","description":"This update for curl fixes the following security issues:\n\n- CVE-2017-1000254: FTP PWD response parser out of bounds read (bsc#1061876)\n","status":"published","published":"2017-10-19T13:20:38Z","modified":"2026-02-04T04:35:54.681526Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2017:2831-1","title":"Security update for curl","description":"This update for curl fixes the following issues:\n\nSecurity issues fixed:\n\n- CVE-2017-1000254: FTP PWD response parser out of bounds read (bsc#1061876)\n- CVE-2017-1000257: IMAP FETCH response out of bounds read (bsc#1063824)\n\nBugs fixed:\n\n- Fixed error 'error:1408F10B:SSL routines' when connecting to ftps via proxy (bsc#1060653)\n\n","status":"published","published":"2017-10-23T06:48:09Z","modified":"2026-02-04T02:44:24.370795Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2017:3176-1","title":"Security update for curl","description":"This update for curl fixes the following security issues:\n\n- CVE-2017-1000254: FTP PWD response parser out of bounds read (bsc#1061876)\n","status":"published","published":"2017-12-01T14:03:23Z","modified":"2026-02-04T03:31:11.10584Z","updated_at":"2026-11-02T15:53:44.209561Z"},{"id":"SUSE-SU-2018:0214-1","title":"Security update for curl","description":"This update for curl fixes several issues.\n\nThese security issues were fixed:\n\n- CVE-2017-1000254: Fix FTP PWD response parser out of bounds read (bsc#1061876).\n- CVE-2018-1000007: Prevent leaking authentication data to third parties when\n  following redirects (bsc#1077001)\n\nAlso the following adjustment was made:\n\n- Set DEFAULT_SUSE as the default cipher list (bsc#1027712)\n","status":"published","published":"2018-01-25T08:36:01Z","modified":"2026-02-04T02:33:56.952623Z","updated_at":"2026-11-02T15:53:44.594517Z"},{"id":"USN-3441-1","title":"curl vulnerabilities","description":"Daniel Stenberg discovered that curl incorrectly handled large floating\npoint output. A remote attacker could use this issue to cause curl to\ncrash, resulting in a denial of service, or possibly execute arbitrary\ncode. This issue only affected Ubuntu 14.04 LTS and Ubuntu 16.04 LTS.\n(CVE-2016-9586)\n\nEven Rouault discovered that curl incorrectly handled large file names when\ndoing TFTP transfers. A remote attacker could use this issue to cause curl\nto crash, resulting in a denial of service, or possibly obtain sensitive\nmemory contents. (CVE-2017-1000100)\n\nBrian Carpenter and Yongji Ouyang discovered that curl incorrectly handled\nnumerical range globbing. A remote attacker could use this issue to cause\ncurl to crash, resulting in a denial of service, or possibly obtain\nsensitive memory contents. (CVE-2017-1000101)\n\nMax Dymond discovered that curl incorrectly handled FTP PWD responses. A\nremote attacker could use this issue to cause curl to crash, resulting in a\ndenial of service. (CVE-2017-1000254)\n\nBrian Carpenter discovered that curl incorrectly handled the --write-out\ncommand line option. A local attacker could possibly use this issue to\nobtain sensitive memory contents. (CVE-2017-7407)\n","status":"published","published":"2017-10-10T12:54:33Z","modified":"2026-04-27T09:13:44.017534Z","updated_at":"2026-11-02T16:58:13.496563Z"}]}}