Overview 239 matches · 0 in Waratek scope · 0 protected · 1 exploited · 0 CISA KEV · 6 public PoC · 4 EPSS ≥ 0.5
239matches
0in Waratek scope0.0%
0protected0.0%
1exploited0.4%
0CISA KEV0.0%
6public PoC2.5%
4EPSS ≥ 0.51.7%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
239
100.0%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
239
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 55 / year
20001
Not applicable1
High1
not blocked1
Working exploit published1
20010
20020
20030
20040
20053
Not applicable3
High2
Medium1
not blocked3
No public exploit3
20061
Not applicable1
High1
not blocked1
No public exploit1
20071
Not applicable1
High1
not blocked1
No public exploit1
20080
20092
Not applicable2
High1
Medium1
not blocked2
Working exploit published1
No public exploit1
20102
Not applicable2
Medium2
not blocked2
No public exploit2
20112
Not applicable2
Medium2
not blocked2
Proof of concept only1
No public exploit1
20121
Not applicable1
High1
not blocked1
No public exploit1
20136
Not applicable6
High2
Medium4
not blocked6
Working exploit published1
No public exploit5
20147
Not applicable7
Medium7
not blocked7
No public exploit7
20159
Not applicable9
High2
Medium7
not blocked9
No public exploit9
20169
Not applicable9
Critical1
High6
Medium2
not blocked9
No public exploit9
201713
Not applicable13
Critical7
High1
Medium4
Low1
not blocked13
No public exploit13
201832
Not applicable32
Critical17
High13
Medium2
not blocked32
No public exploit32
20198
Not applicable8
Critical3
High4
Low1
not blocked8
No public exploit8
20209
Not applicable9
Critical3
High5
Low1
not blocked9
Proof of concept only2
No public exploit7
202115
Not applicable15
Critical2
High3
Medium8
Low2
not blocked15
Proof of concept only10
Forecast only1
No public exploit4
202222
Not applicable22
Critical3
High9
Medium9
Low1
not blocked22
Exploited1
Proof of concept only14
No public exploit7
202320
Not applicable20
Critical3
High4
Medium11
Low2
not blocked20
Proof of concept only14
No public exploit6
202412
Not applicable12
High2
Medium8
Low2
not blocked12
Proof of concept only4
No public exploit8
20259
Not applicable9
High4
Medium4
Low1
not blocked9
Proof of concept only5
No public exploit4
202655
Not applicable55
Critical10
High28
Medium16
Low1
not blocked55
Proof of concept only35
No public exploit20
200220052008201120142017202020232026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2016-4802 | High | 2016-06-24 | Not applicable | No public exploit | Multiple untrusted search path vulnerabilities in cURL and libcurl before 7.49.1, when built with SSPI or telnet is enabled, allow local users to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse (1) security.dll, (2) secur32.dll, or (3) ws2_32.dll in the application or current working directory. |
| CVE-2016-3739 | Medium | 2016-05-20 | Not applicable | No public exploit | The (1) mbed_connect_step1 function in lib/vtls/mbedtls.c and (2) polarssl_connect_step1 function in lib/vtls/polarssl.c in cURL and libcurl before 7.49.0, when using SSLv3 or making a TLS connection to a URL that uses a numerical IP address, allow remote attackers to spoof servers via an arbitrary valid certificate. |
| CVE-2016-0755 | High | 2016-01-29 | Not applicable | No public exploit | The ConnectionExists function in lib/url.c in libcurl before 7.47.0 does not properly re-use NTLM-authenticated proxy connections, which might allow remote attackers to authenticate as other users via a request, a similar issue to CVE-2014-0015. |
| CVE-2016-0754 | Medium | 2016-01-29 | Not applicable | No public exploit | cURL before 7.47.0 on Windows allows attackers to write to arbitrary files in the current working directory on a different drive via a colon in a remote file name. |
| CVE-2015-3237 | Medium | 2015-06-22 | Not applicable | No public exploit | The smb_request_state function in cURL and libcurl 7.40.0 through 7.42.1 allows remote SMB servers to obtain sensitive information from memory or cause a denial of service (out-of-bounds read and crash) via crafted length and offset values. |
| CVE-2015-3236 | Medium | 2015-06-22 | Not applicable | No public exploit | cURL and libcurl 7.40.0 through 7.42.1 send the HTTP Basic authentication credentials for a previous connection when reusing a reset (curl_easy_reset) connection handle to send a request to the same host name, which allows remote attackers to obtain sensitive information via unspecified vectors. |
| CVE-2015-3153 | Medium | 2015-05-01 | Not applicable | No public exploit | 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. |
| CVE-2015-3148 | Medium | 2015-04-24 | Not applicable | No public exploit | 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. |
| CVE-2015-3145 | High | 2015-04-24 | Not applicable | No public exploit | The sanitize_cookie_path function in cURL and libcurl 7.31.0 through 7.41.0 does not properly calculate an index, which allows remote attackers to cause a denial of service (out-of-bounds write and crash) or possibly have other unspecified impact via a cookie path containing only a double-quote character. |
| CVE-2015-3144 | High | 2015-04-24 | Not applicable | No public exploit | The fix_hostname function in cURL and libcurl 7.37.0 through 7.41.0 does not properly calculate an index, which allows remote attackers to cause a denial of service (out-of-bounds read or write and crash) or possibly have other unspecified impact via a zero-length host name, as demonstrated by "http://:80" and ":80." |
| CVE-2015-3143 | Medium | 2015-04-24 | Not applicable | No public exploit | 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. |
| CVE-2014-8151 | Medium | 2015-01-15 | Not applicable | No public exploit | The darwinssl_connect_step1 function in lib/vtls/curl_darwinssl.c in libcurl 7.31.0 through 7.39.0, when using the DarwinSSL (aka SecureTransport) back-end for TLS, does not check if a cached TLS session validated the certificate when reusing the session, which allows man-in-the-middle attackers to spoof servers via a crafted certificate. |
| CVE-2014-8150 | Medium | 2015-01-15 | Not applicable | No public exploit | 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. |
| CVE-2014-3620 | Medium | 2014-11-18 | Not applicable | No public exploit | cURL and libcurl before 7.38.0 allow remote attackers to bypass the Same Origin Policy and set cookies for arbitrary sites by setting a cookie for a top-level domain. |
| CVE-2014-3613 | Medium | 2014-11-18 | Not applicable | No public exploit | cURL and libcurl before 7.38.0 does not properly handle IP addresses in cookie domain names, which allows remote attackers to set cookies for or send arbitrary cookies to certain sites, as demonstrated by a site at 192.168.0.1 setting cookies for a site at 127.168.0.1. |
| CVE-2014-3707 | Medium | 2014-11-15 | Not applicable | No public exploit | The curl_easy_duphandle function in libcurl 7.17.1 through 7.38.0, when running with the CURLOPT_COPYPOSTFIELDS option, does not properly copy HTTP POST data for an easy handle, which triggers an out-of-bounds read that allows remote web servers to read sensitive memory information. |
| CVE-2014-2522 | Medium | 2014-04-18 | Not applicable | No public exploit | curl and libcurl 7.27.0 through 7.35.0, when running on Windows and using the SChannel/Winssl TLS backend, does not verify that the server hostname matches a domain name in the subject's Common Name (CN) or subjectAltName field of the X.509 certificate when accessing a URL that uses a numerical IP address, which allows man-in-the-middle attackers to spoof servers via an arbitrary valid certificate. |
| CVE-2014-0139 | Medium | 2014-04-15 | Not applicable | No public exploit | 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. |
| CVE-2014-0138 | Medium | 2014-04-15 | Not applicable | No public exploit | The default configuration in cURL and libcurl 7.10.6 before 7.36.0 re-uses (1) SCP, (2) SFTP, (3) POP3, (4) POP3S, (5) IMAP, (6) IMAPS, (7) SMTP, (8) SMTPS, (9) LDAP, and (10) LDAPS connections, which might allow context-dependent attackers to connect as other users via a request, a similar issue to CVE-2014-0015. |
| CVE-2014-0015 | Medium | 2014-02-02 | Not applicable | No public exploit | cURL and libcurl 7.10.6 through 7.34.0, when more than one authentication method is enabled, re-uses NTLM connections, which might allow context-dependent attackers to authenticate as other users via a request. |
| CVE-2013-6422 | Medium | 2013-12-23 | Not applicable | No public exploit | The GnuTLS backend in libcurl 7.21.4 through 7.33.0, when disabling digital signature verification (CURLOPT_SSL_VERIFYPEER), also disables the CURLOPT_SSL_VERIFYHOST check for CN or SAN host name fields, which makes it easier for remote attackers to spoof servers and conduct man-in-the-middle (MITM) attacks. |
| CVE-2013-4545 | Medium | 2013-11-23 | Not applicable | No public exploit | cURL and libcurl 7.18.0 through 7.32.0, when built with OpenSSL, disables the certificate CN and SAN name field verification (CURLOPT_SSL_VERIFYHOST) when the digital signature verification (CURLOPT_SSL_VERIFYPEER) is disabled, which allows man-in-the-middle attackers to spoof SSL servers via an arbitrary valid certificate. |
| CVE-2013-2174 | Medium | 2013-07-31 | Not applicable | No public exploit | Heap-based buffer overflow in the curl_easy_unescape function in lib/escape.c in cURL and libcurl 7.7 through 7.30.0 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted string ending in a "%" (percent) character. |
| CVE-2013-1944 | Medium | 2013-04-29 | Not applicable | No public exploit | The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL. |
| CVE-2013-2617 | High | 2013-03-20 | Not applicable | No public exploit | lib/curl.rb in the Curl Gem for Ruby allows remote attackers to execute arbitrary commands via shell metacharacters in a URL. |
| CVE-2013-0249 | High | 2013-03-08 | Not applicable | Working exploit published | Stack-based buffer overflow in the Curl_sasl_create_digest_md5_message function in lib/curl_sasl.c in curl and libcurl 7.26.0 through 7.28.1, when negotiating SASL DIGEST-MD5 authentication, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long string in the realm parameter in a (1) POP3, (2) SMTP or (3) IMAP message. |
| CVE-2012-0036 | High | 2012-04-13 | Not applicable | No public exploit | curl and libcurl 7.2x before 7.24.0 do not properly consider special characters during extraction of a pathname from a URL, which allows remote attackers to conduct data-injection attacks via a crafted URL, as demonstrated by a CRLF injection attack on the (1) IMAP, (2) POP3, or (3) SMTP protocol. |
| CVE-2011-3389 | Medium | 2011-09-06 | Not applicable | Proof of concept only | The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack. |
| CVE-2011-2192 | Medium | 2011-07-07 | Not applicable | No public exploit | The Curl_input_negotiate function in http_negotiate.c in libcurl 7.10.6 through 7.21.6, as used in curl and other products, always performs credential delegation during GSSAPI authentication, which allows remote servers to impersonate clients via GSSAPI requests. |
| CVE-2010-3842 | Medium | 2010-10-28 | Not applicable | No public exploit | Absolute path traversal vulnerability in curl 7.20.0 through 7.21.1, when the --remote-header-name or -J option is used, allows remote servers to create or overwrite arbitrary files by using \ (backslash) as a separator of path components within the Content-disposition HTTP header. |
| CVE-2010-0734 | Medium | 2010-03-19 | Not applicable | No public exploit | content_encoding.c in libcurl 7.10.5 through 7.19.7, when zlib is enabled, does not properly restrict the amount of callback data sent to an application that requests automatic decompression, which might allow remote attackers to cause a denial of service (application crash) or have unspecified other impact by sending crafted compressed data to an application that relies on the intended data-length limit. |
| CVE-2009-2417 | High | 2009-08-14 | Not applicable | No public exploit | lib/ssluse.c in cURL and libcurl 7.4 through 7.19.5, when OpenSSL is used, does not properly handle a '\0' character in a domain name in the subject's Common Name (CN) field of an X.509 certificate, which allows man-in-the-middle attackers to spoof arbitrary SSL servers via a crafted certificate issued by a legitimate Certification Authority, a related issue to CVE-2009-2408. |
| CVE-2009-0037 | Medium | 2009-03-05 | Not applicable | Working exploit published | The redirect implementation in curl and libcurl 5.11 through 7.19.3, when CURLOPT_FOLLOWLOCATION is enabled, accepts arbitrary Location values, which might allow remote HTTP servers to (1) trigger arbitrary requests to intranet servers, (2) read or overwrite arbitrary files via a redirect to a file: URL, or (3) execute arbitrary commands via a redirect to an scp: URL. |
| CVE-2007-3564 | High | 2007-07-18 | Not applicable | No public exploit | libcurl 7.14.0 through 7.16.3, when built with GnuTLS support, does not check SSL/TLS certificate expiration or activation dates, which allows remote attackers to bypass certain access restrictions. |
| CVE-2006-1061 | High | 2006-03-21 | Not applicable | No public exploit | Heap-based buffer overflow in cURL and libcURL 7.15.0 through 7.15.2 allows remote attackers to execute arbitrary commands via a TFTP URL (tftp://) with a valid hostname and a long path. |
| CVE-2005-4077 | Medium | 2005-12-08 | Not applicable | No public exploit | Multiple off-by-one errors in the cURL library (libcurl) 7.11.2 through 7.15.0 allow local users to trigger a buffer overflow and cause a denial of service or bypass PHP security restrictions via certain URLs that (1) are malformed in a way that prevents a terminating null byte from being added to either a hostname or path buffer, or (2) contain a "?" separator in the hostname portion, which causes a "/" to be prepended to the resulting string. |
| CVE-2005-3185 | High | 2005-10-13 | Not applicable | No public exploit | Stack-based buffer overflow in the ntlm_output function in http-ntlm.c for (1) wget 1.10, (2) curl 7.13.2, and (3) libcurl 7.13.2, and other products that use libcurl, when NTLM authentication is enabled, allows remote servers to execute arbitrary code via a long NTLM username. |
| CVE-2005-0490 | High | 2005-05-02 | Not applicable | No public exploit | Multiple stack-based buffer overflows in libcURL and cURL 7.12.1, and possibly other versions, allow remote malicious web servers to execute arbitrary code via base64 encoded replies that exceed the intended buffer lengths when decoded, which is not properly handled by (1) the Curl_input_ntlm function in http_ntlm.c during NTLM authentication or (2) the Curl_krb_kauth and krb4_auth functions in krb4.c during Kerberos authentication. |
| CVE-2000-0973 | High | 2000-12-19 | Not applicable | Working exploit published | Buffer overflow in curl earlier than 6.0-1.1, and curl-ssl earlier than 6.0-1.2, allows remote attackers to execute arbitrary commands by forcing a long error message to be generated. |