CVE-2015-3153
The default configuration for cURL and libcurl before 7.42.1 sends custom HTTP headers to both...
The default configuration for cURL and libcurl before 7.42.1 sends custom HTTP headers to both the proxy and destination server, which might allow remote proxy servers to obtain sensitive information by reading the header contents.
Exploit likelihood
What each source reports
NVD Score used
5.0
The default configuration for cURL and libcurl before 7.42.1 sends custom HTTP headers to both the proxy and destination server, which might allow remote proxy servers to obtain sensitive information by reading the header contents.
- Record
CVE-2015-3153- CVSS 2.0
- 5.0 Medium
AV:N/AC:L/Au:N/C:P/I:N/A:N - Weakness
- CWE-200
- Updated
- 2026-11-02
CVE List No score
The default configuration for cURL and libcurl before 7.42.1 sends custom HTTP headers to both the proxy and destination server, which might allow remote proxy servers to obtain sensitive information by reading the header contents.
- Record
CVE-2015-3153- Updated
- 2026-11-02
EUVDEUVD-2015-3234 No score
The default configuration for cURL and libcurl before 7.42.1 sends custom HTTP headers to both the proxy and destination server, which might allow remote proxy servers to obtain sensitive information by reading the header contents.
- Record
EUVD-2015-3234- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-hwj5-x3jv-hmff No score
The default configuration for cURL and libcurl before 7.42.1 sends custom HTTP headers to both...
The default configuration for cURL and libcurl before 7.42.1 sends custom HTTP headers to both the proxy and destination server, which might allow remote proxy servers to obtain sensitive information by reading the header contents.
- Record
GHSA-hwj5-x3jv-hmff- Weakness
- CWE-200
- Updated
- 2026-11-02
OSVCURL-CVE-2015-3153 No score
sensitive HTTP server headers also sent to proxies
libcurl provides applications a way to set custom HTTP headers to be sent to
the server by using CURLOPT_HTTPHEADER. A similar option is available for
the curl command-line tool with the '--header' option.
When the connection passes through an HTTP proxy the same set of headers is sent to the proxy as well by default. While this is by design, it has not necessarily been clear nor understood by application programmers.
Such tunneling over a proxy is done for example when using the HTTPS protocol
- or when explicitly asked for. In this case, the initial connection to the proxy is made in clear including any custom headers using the HTTP CONNECT method.
While libcurl provides the CURLOPT_HEADEROPT option to allow applications to
tell libcurl if the headers should be sent to host and the proxy or use
separate lists to the different destinations, it has still defaulted to
sending the same headers to both parties for the sake of compatibility.
If the application sets a custom HTTP header with sensitive content (e.g., authentication cookies) without changing the default, the proxy, and anyone who listens to the traffic between the application and the proxy, might get access to those values.
Note: this problem does not exist when using the CURLOPT_COOKIE option (or
the --cookie option) or the HTTP auth options, which are always sent only to
the destination server.
- Record
CURL-CVE-2015-3153- Updated
- 2026-11-02
OSV No score
The default configuration for cURL and libcurl before 7.42.1 sends custom HTTP headers to both the proxy and destination server, which might allow remote proxy servers to obtain sensitive information by reading the header contents.
- Record
CVE-2015-3153- Updated
- 2026-11-02
Show 6 moreShow less
OSVDEBIAN-CVE-2015-3153 No score
The default configuration for cURL and libcurl before 7.42.1 sends custom HTTP headers to both the proxy and destination server, which might allow remote proxy servers to obtain sensitive information by reading the header contents.
- Record
DEBIAN-CVE-2015-3153- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:10303-1 No score
curl-7.51.0-1.1 on GA media
These are all security issues fixed in the curl-7.51.0-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:10303-1- Updated
- 2026-11-02
OSVSUSE-SU-2015:0962-1 No score
Security update for curl
This curl update fixes the following security issues:
* bnc#868627: wrong re-use of connections (CVE-2014-0138).
* bnc#868629: IP address wildcard certificate validation
(CVE-2014-0139).
* bnc#870444: --insecure option inappropriately enforcing security
safeguard.
Security Issue references:
* CVE-2014-0138
<http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0138>
* CVE-2014-0139
<http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0139>
- Record
SUSE-SU-2015:0962-1- Updated
- 2026-11-02
OSVSUSE-SU-2015:0990-1 No score
Security update for curl
curl was updated to fix five security issues.
The following vulnerabilities were fixed:
- CVE-2015-3143: curl could re-use NTML authenticateds connections
- CVE-2015-3144: curl could access memory out of bounds with zero length host names
- CVE-2015-3145: curl cookie parser could access memory out of boundary
- CVE-2015-3148: curl could treat Negotiate as not connection-oriented
- CVE-2015-3153: curl could have sent sensitive HTTP headers also to proxies
- Record
SUSE-SU-2015:0990-1- Updated
- 2026-11-02
OSVUBUNTU-CVE-2015-3153 No score
The default configuration for cURL and libcurl before 7.42.1 sends custom HTTP headers to both the proxy and destination server, which might allow remote proxy servers to obtain sensitive information by reading the header contents.
- Record
UBUNTU-CVE-2015-3153- Updated
- 2026-11-02
OSVUSN-2591-1 No score
curl vulnerabilities
Paras Sethia discovered that curl could incorrectly re-use NTLM HTTP credentials when subsequently connecting to the same host over HTTP. (CVE-2015-3143)
Hanno Böck discovered that curl incorrectly handled zero-length host names. If a user or automated system were tricked into using a specially crafted host name, an attacker could possibly use this issue to cause curl to crash, resulting in a denial of service, or possibly execute arbitrary code. This issue only affected Ubuntu 14.10 and Ubuntu 15.04. (CVE-2015-3144)
Hanno Böck discovered that curl incorrectly handled cookie path elements. If a user or automated system were tricked into parsing a specially crafted cookie, an attacker could possibly use this issue to cause curl to crash, resulting in a denial of service, or possibly execute arbitrary code. This issue only affected Ubuntu 14.04 LTS, Ubuntu 14.10 and Ubuntu 15.04. (CVE-2015-3145)
Isaac Boukris discovered that when using Negotiate authenticated connections, curl could incorrectly authenticate the entire connection and not just specific HTTP requests. (CVE-2015-3148)
Yehezkel Horowitz and Oren Souroujon discovered that curl sent HTTP headers both to servers and proxies by default, contrary to expectations. This issue only affected Ubuntu 14.10 and Ubuntu 15.04. (CVE-2015-3153)
- Record
USN-2591-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
curlDebian:12 |
before 7.42.1-1 | 7.42.1-1 |
curlDebian:13 |
before 7.42.1-1 | 7.42.1-1 |
curlDebian:14 |
before 7.42.1-1 | 7.42.1-1 |
curlDebian:8 |
before 7.38.0-4+deb8u2, plus listed versions 7.38.0-47.38.0-4+deb8u1 |
7.38.0-4+deb8u2 |
curlSUSE:Linux Enterprise Desktop 12 From an advisory covering 5 CVEs |
before 7.37.0-15.1 | 7.37.0-15.1 |
curlSUSE:Linux Enterprise Software Development Kit 12 From an advisory covering 5 CVEs |
before 7.37.0-15.1 | 7.37.0-15.1 |
curlSUSE:Linux Enterprise Server 12 From an advisory covering 5 CVEs |
before 7.37.0-15.1 | 7.37.0-15.1 |
curlSUSE:Linux Enterprise Server for SAP Applications 12 From an advisory covering 5 CVEs |
before 7.37.0-15.1 | 7.37.0-15.1 |
curlUbuntu:Pro:14.04:LTS |
All versions, plus listed versions 7.32.0-1ubuntu17.33.0-1ubuntu17.34.0-1ubuntu17.35.0-1ubuntu17.35.0-1ubuntu2 Show 41 moreShow less7.35.0-1ubuntu2.17.35.0-1ubuntu2.27.35.0-1ubuntu2.37.35.0-1ubuntu2.57.35.0-1ubuntu2.67.35.0-1ubuntu2.77.35.0-1ubuntu2.87.35.0-1ubuntu2.97.35.0-1ubuntu2.107.35.0-1ubuntu2.117.35.0-1ubuntu2.127.35.0-1ubuntu2.137.35.0-1ubuntu2.147.35.0-1ubuntu2.157.35.0-1ubuntu2.167.35.0-1ubuntu2.177.35.0-1ubuntu2.197.35.0-1ubuntu2.207.35.0-1ubuntu2.20+esm27.35.0-1ubuntu2.20+esm37.35.0-1ubuntu2.20+esm47.35.0-1ubuntu2.20+esm57.35.0-1ubuntu2.20+esm67.35.0-1ubuntu2.20+esm77.35.0-1ubuntu2.20+esm87.35.0-1ubuntu2.20+esm97.35.0-1ubuntu2.20+esm107.35.0-1ubuntu2.20+esm117.35.0-1ubuntu2.20+esm127.35.0-1ubuntu2.20+esm137.35.0-1ubuntu2.20+esm147.35.0-1ubuntu2.20+esm157.35.0-1ubuntu2.20+esm167.35.0-1ubuntu2.20+esm177.35.0-1ubuntu2.20+esm187.35.0-1ubuntu2.20+esm197.35.0-1ubuntu2.20+esm207.35.0-1ubuntu2.20+esm217.35.0-1ubuntu2.20+esm227.35.0-1ubuntu2.20+esm237.35.0-1ubuntu2.20+esm24 |
None known |
curlUbuntu:14.04:LTS From an advisory covering 5 CVEs |
before 7.35.0-1ubuntu2.5, plus listed versions 7.32.0-1ubuntu17.33.0-1ubuntu17.34.0-1ubuntu17.35.0-1ubuntu17.35.0-1ubuntu27.35.0-1ubuntu2.17.35.0-1ubuntu2.27.35.0-1ubuntu2.3 |
7.35.0-1ubuntu2.5 |
curlopenSUSE:Tumbleweed From an advisory covering 32 CVEs |
before 7.51.0-1.1 | 7.51.0-1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2015-3153 is a medium vulnerability (CVSS 5.0) in Haxx Curl, published April 15, 2014. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 7.34%, the 94th percentile. Fixed in curl 7.42.1-1.
References
kc.mcafee.com/corporate/index?page=content&id=SB10131
securitytracker.com/id/1032233
oracle.com/technetwork/topics/security/cpuoct2015-2367953.html
oracle.com/technetwork/topics/security/cpujan2016-2367955.html
ubuntu.com/usn/USN-2591-1
lists.opensuse.org/opensuse-updates/2015-05/msg00017.html
Show 64 moreShow less
lists.apple.com/archives/security-announce/2015/Aug/msg00001.html
oracle.com/technetwork/security-advisory/cpuoct2018-4428296.html
kb.juniper.net/InfoCenter/index?page=content&id=JSA10743
oracle.com/technetwork/topics/security/bulletinjan2016-2867206.html
support.apple.com/kb/HT205031
securityfocus.com/bid/74408
curl.haxx.se/docs/adv_20150429.html
debian.org/security/2015/dsa-3240
nvd.nist.gov/vuln/detail/CVE-2015-3153
github.com/advisories/GHSA-hwj5-x3jv-hmff
security-tracker.debian.org/tracker/CVE-2015-3153
suse.com/support/update/announcement/2015/suse-su-20150962-1
bugzilla.suse.com/824517
bugzilla.suse.com/849596
bugzilla.suse.com/858673
bugzilla.suse.com/868627
bugzilla.suse.com/868629
bugzilla.suse.com/870444
bugzilla.suse.com/927174
bugzilla.suse.com/927556
bugzilla.suse.com/927746
bugzilla.suse.com/928533
suse.com/security/cve/CVE-2013-2174
suse.com/security/cve/CVE-2013-4545
suse.com/security/cve/CVE-2014-0015
suse.com/security/cve/CVE-2014-0138
suse.com/security/cve/CVE-2014-0139
suse.com/security/cve/CVE-2015-3143
suse.com/security/cve/CVE-2015-3148
suse.com/security/cve/CVE-2015-3153
suse.com/support/update/announcement/2015/suse-su-20150990-1
bugzilla.suse.com/927607
bugzilla.suse.com/927608
suse.com/security/cve/CVE-2015-3144
suse.com/security/cve/CVE-2015-3145
ubuntu.com/security/CVE-2015-3153
ubuntu.com/security/notices/USN-2591-1
cve.org/CVERecord?id=CVE-2015-3153
ubuntu.com/security/CVE-2015-3143
ubuntu.com/security/CVE-2015-3144
ubuntu.com/security/CVE-2015-3145
ubuntu.com/security/CVE-2015-3148
suse.com/security/cve/CVE-2009-0037
suse.com/security/cve/CVE-2009-2417
suse.com/security/cve/CVE-2013-0249
suse.com/security/cve/CVE-2013-1944
suse.com/security/cve/CVE-2014-3613
suse.com/security/cve/CVE-2014-3620
suse.com/security/cve/CVE-2014-8150
suse.com/security/cve/CVE-2015-3236
suse.com/security/cve/CVE-2015-3237
suse.com/security/cve/CVE-2016-0755
suse.com/security/cve/CVE-2016-7167
suse.com/security/cve/CVE-2016-8615
suse.com/security/cve/CVE-2016-8616
suse.com/security/cve/CVE-2016-8617
suse.com/security/cve/CVE-2016-8618
suse.com/security/cve/CVE-2016-8619
suse.com/security/cve/CVE-2016-8620
suse.com/security/cve/CVE-2016-8621
suse.com/security/cve/CVE-2016-8622
suse.com/security/cve/CVE-2016-8623
suse.com/security/cve/CVE-2016-8624
suse.com/security/cve/CVE-2016-8625