First published: Fri May 01 2015(Updated: )
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.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
Oracle Enterprise Manager Ops Center | <=12.1.3 | |
Oracle Enterprise Manager Ops Center | =12.2.0 | |
Oracle Enterprise Manager Ops Center | =12.2.1 | |
Oracle Enterprise Manager Ops Center | =12.3.0 | |
Curl | <=7.42.0 | |
libcurl | <=7.42.0 | |
Ubuntu | =12.04 | |
Ubuntu | =14.04 | |
Ubuntu | =14.10 | |
Ubuntu | =15.1 | |
Apple iOS and macOS | =10.10.4 | |
Debian | =8.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-3153 is classified as a high severity vulnerability due to the potential exposure of sensitive information.
To fix CVE-2015-3153, you should upgrade to cURL and libcurl version 7.42.1 or later.
CVE-2015-3153 affects multiple versions of cURL, libcurl, and Oracle Enterprise Manager Ops Center.
The impact of CVE-2015-3153 includes the risk of remote proxy servers accessing sensitive information through custom HTTP headers.
Yes, a patch is available in the form of upgraded versions of cURL and libcurl, specifically version 7.42.1 and later.