Haxx libcurl 7.11.1
Approved changes feed: RSS · Atom
cpe:2.3:a:haxx:libcurl:7.11.1:*:*:*:*:*:*:*
part: a version: 7.11.1 update: *
| Vendor | Haxx (d671a1c6-5c93-5e0c-94d0-7f7092cb4b41) |
|---|---|
| Product | Libcurl (3b3523ef-9710-50bf-8391-80ac7eb566e1) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:curl/libcurl |
purl2cpe | 2026-06-01 10:12:18.984713 |
pkg:deb/debian/curl |
purl2cpe | 2026-06-01 10:12:18.984715 |
pkg:deb/ubuntu/curl |
purl2cpe | 2026-06-01 10:12:18.984716 |
pkg:github/curl/curl |
purl2cpe | 2026-06-01 10:12:18.984717 |
pkg:rpm/fedora/curl |
purl2cpe | 2026-06-01 10:12:18.984719 |
pkg:rpm/opensuse/curl |
purl2cpe | 2026-06-01 10:12:18.984720 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2017-1000254 |
vulnerable | 2026-06-08 05:08:34.372911 |
Details available
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.
Published: 2017-10-06T13:00:00.000Z
Updated: 2024-08-05T22:00:39.675Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2015-3148 |
vulnerable | 2026-06-08 05:06:37.287120 |
Details available
cURL and libcurl 7.10.6 through 7.41.0 do not properly re-use authenticated Negotiate connections, which allows remote attackers to connect as other users via a request.
Published: 2015-04-24T14:00:00.000Z
Updated: 2024-08-06T05:39:31.988Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2015-3143 |
vulnerable | 2026-06-08 05:06:37.227189 |
Details available
cURL and libcurl 7.10.6 through 7.41.0 does not properly re-use NTLM connections, which allows remote attackers to connect as other users via an unauthenticated request, a similar issue to CVE-2014-0015.
Published: 2015-04-24T14:00:00.000Z
Updated: 2024-08-06T05:39:31.921Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2014-8150 |
vulnerable | 2026-06-08 05:06:08.161982 |
Details available
CRLF injection vulnerability in libcurl 6.0 through 7.x before 7.40.0, when using an HTTP proxy, allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via CRLF sequences in a URL.
Published: 2015-01-15T15:00:00.000Z
Updated: 2024-08-06T13:10:50.913Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2014-0139 |
vulnerable | 2026-06-08 05:05:11.774769 |
Details available
cURL and libcurl 7.1 before 7.36.0, when using the OpenSSL, axtls, qsossl or gskit libraries for TLS, recognize a wildcard IP address in the subject's Common Name (CN) field of an X.509 certificate, which might allow man-in-the-middle attackers to spoof arbitrary SSL servers via a crafted certificate issued by a legitimate Certification Authority.
Published: 2014-04-15T14:00:00.000Z
Updated: 2024-08-06T09:05:38.790Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2014-0138 |
vulnerable | 2026-06-08 05:05:11.765170 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2014-0015 |
vulnerable | 2026-06-08 05:05:10.595591 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2013-2174 |
vulnerable | 2026-06-08 05:03:58.810039 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.