Search for packages
| purl | pkg:generic/curl.se/curl@7.17.0 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-1bg9-85q6-bya3
Aliases: CVE-2018-14618 |
curl before version 7.61.1 is vulnerable to a buffer overrun in the NTLM authentication code. The internal function Curl_ntlm_core_mk_nt_hash multiplies the length of the password by two (SUM) to figure out how large temporary storage area to allocate from the heap. The length value is then subsequently used to iterate over the password and generate output into the allocated storage buffer. On systems with a 32 bit size_t, the math to calculate SUM triggers an integer overflow when the password length exceeds 2GB (2^31 bytes). This integer overflow usually causes a very small buffer to actually get allocated instead of the intended very huge one, making the use of that buffer end up in a heap buffer overflow. (This bug is almost identical to CVE-2017-8816.) |
Affected by 51 other vulnerabilities. |
|
VCID-3hax-q2kc-eye5
Aliases: CVE-2018-1000120 GHSA-674j-7m97-j2p9 |
A buffer overflow exists in curl 7.12.3 to and including curl 7.58.0 in the FTP URL handling that allows an attacker to cause a denial of service or worse. |
Affected by 54 other vulnerabilities. |
|
VCID-3j31-rzu1-dkc9
Aliases: CVE-2014-0138 |
Affected by 86 other vulnerabilities. |
|
|
VCID-3pz4-p8n7-mfe7
Aliases: CVE-2016-8617 |
The base64 encode function in curl before version 7.51.0 is prone to a buffer being under allocated in 32bit systems if it receives at least 1Gb as input via `CURLOPT_USERNAME`. |
Affected by 63 other vulnerabilities. |
|
VCID-4mdh-6sq4-vqfc
Aliases: CVE-2023-27535 |
An authentication bypass vulnerability exists in libcurl <8.0.0 in the FTP connection reuse feature that can result in wrong credentials being used during subsequent transfers. Previously created connections are kept in a connection pool for reuse if they match the current setup. However, certain FTP settings such as CURLOPT_FTP_ACCOUNT, CURLOPT_FTP_ALTERNATIVE_TO_USER, CURLOPT_FTP_SSL_CCC, and CURLOPT_USE_SSL were not included in the configuration match checks, causing them to match too easily. This could lead to libcurl using the wrong credentials when performing a transfer, potentially allowing unauthorized access to sensitive information. |
Affected by 19 other vulnerabilities. |
|
VCID-67tv-9g7a-eqhe
Aliases: CVE-2014-0139 |
Affected by 86 other vulnerabilities. |
|
|
VCID-6g4s-g758-gyek
Aliases: CVE-2016-8624 |
curl before version 7.51.0 doesn't parse the authority component of the URL correctly when the host name part ends with a '#' character, and could instead be tricked into connecting to a different host. This may have security implications if you for example use an URL parser that follows the RFC to check for allowed domains before using curl to request them. |
Affected by 63 other vulnerabilities. |
|
VCID-7958-m7nd-tuet
Aliases: CVE-2016-4802 |
Windows DLL hijacking |
Affected by 79 other vulnerabilities. |
|
VCID-7b6t-h7w2-a7am
Aliases: CVE-2022-32208 |
When curl < 7.84.0 does FTP transfers secured by krb5, it handles message verification failures wrongly. This flaw makes it possible for a Man-In-The-Middle attack to go unnoticed and even allows it to inject data to the client. |
Affected by 32 other vulnerabilities. |
|
VCID-7c3e-97qs-ube7
Aliases: CVE-2016-8621 |
The `curl_getdate` function in curl before version 7.51.0 is vulnerable to an out of bounds read if it receives an input with one digit short. |
Affected by 63 other vulnerabilities. |
|
VCID-7cxc-5tec-g3gm
Aliases: CVE-2022-27776 |
A insufficiently protected credentials vulnerability in fixed in curl 7.83.0 might leak authentication or cookie header data on HTTP redirects to the same host but another port number. |
Affected by 39 other vulnerabilities. |
|
VCID-7g8x-2u49-myfk
Aliases: CVE-2009-0037 |
Affected by 62 other vulnerabilities. |
|
|
VCID-9ebs-w43b-h7as
Aliases: CVE-2016-0754 |
remote filename path traversal in curl tool for Windows |
Affected by 80 other vulnerabilities. |
|
VCID-9n9j-kk6t-jfdw
Aliases: CVE-2018-16842 |
Curl versions 7.14.1 through 7.61.1 are vulnerable to a heap-based buffer over-read in the tool_msgs.c:voutf() function that may result in information exposure and denial of service. |
Affected by 50 other vulnerabilities. |
|
VCID-9tk9-a11p-r7fb
Aliases: CVE-2017-7407 |
Affected by 61 other vulnerabilities. |
|
|
VCID-a3bj-tpnb-ekc8
Aliases: CVE-2016-8616 |
A flaw was found in curl before version 7.51.0 When re-using a connection, curl was doing case insensitive comparisons of user name and password with the existing connections. This means that if an unused connection with proper credentials exists for a protocol that has connection-scoped credentials, an attacker can cause that connection to be reused if s/he knows the case-insensitive version of the correct password. |
Affected by 63 other vulnerabilities. |
|
VCID-a63f-dgdt-qkeu
Aliases: CVE-2023-28321 |
An improper certificate validation vulnerability exists in curl <v8.1.0 in the way it supports matching of wildcard patterns when listed as "Subject Alternative Name" in TLS server certificates. curl can be built to use its own name matching function for TLS rather than one provided by a TLS library. This private wildcard matching function would match IDN (International Domain Name) hosts incorrectly and could as a result accept patterns that otherwise should mismatch. IDN hostnames are converted to puny code before used for certificate checks. Puny coded names always start with `xn--` and should not be allowed to pattern match, but the wildcard check in curl could still check for `x*`, which would match even though the IDN name most likely contained nothing even resembling an `x`. |
Affected by 15 other vulnerabilities. |
|
VCID-ae2d-dcng-pfe9
Aliases: CVE-2017-1000100 |
Affected by 60 other vulnerabilities. |
|
|
VCID-b3n4-qjn2-x7dx
Aliases: CVE-2023-28322 |
An information disclosure vulnerability exists in curl <v8.1.0 when doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously wasused to issue a `PUT` request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the second transfer. The problem exists in the logic for a reused handle when it is (expected to be) changed from a PUT to a POST. |
Affected by 15 other vulnerabilities. |
|
VCID-bfvw-myxs-u7fn
Aliases: CVE-2016-8623 |
A flaw was found in curl before version 7.51.0. The way curl handles cookies permits other threads to trigger a use-after-free leading to information disclosure. |
Affected by 63 other vulnerabilities. |
|
VCID-bmc9-d3cf-nfc4
Aliases: CVE-2015-3148 |
Affected by 82 other vulnerabilities. |
|
|
VCID-cf1z-1bxk-r7hs
Aliases: CVE-2013-2174 |
Affected by 81 other vulnerabilities. |
|
|
VCID-d5k5-2r4p-tqat
Aliases: CVE-2016-9586 |
curl before version 7.52.0 is vulnerable to a buffer overflow when doing a large floating point output in libcurl's implementation of the printf() functions. If there are any application that accepts a format string from the outside without necessary input filtering, it could allow remote attacks. |
Affected by 64 other vulnerabilities. |
|
VCID-dt8u-p2t3-mbfv
Aliases: CVE-2016-8618 |
The libcurl API function called `curl_maprintf()` before version 7.51.0 can be tricked into doing a double-free due to an unsafe `size_t` multiplication, on systems using 32 bit `size_t` variables. |
Affected by 63 other vulnerabilities. |
|
VCID-dw2d-6fkr-87g2
Aliases: CVE-2023-28320 |
A denial of service vulnerability exists in curl <v8.1.0 in the way libcurl provides several different backends for resolving host names, selected at build time. If it is built to use the synchronous resolver, it allows name resolves to time-out slow operations using `alarm()` and `siglongjmp()`. When doing this, libcurl used a global buffer that was not mutex protected and a multi-threaded application might therefore crash or otherwise misbehave. |
Affected by 15 other vulnerabilities. |
|
VCID-fnu8-rhf3-9uat
Aliases: CVE-2021-22876 |
Affected by 44 other vulnerabilities. |
|
|
VCID-g7m2-cu4w-abes
Aliases: CVE-2023-27538 |
An authentication bypass vulnerability exists in libcurl prior to v8.0.0 where it reuses a previously established SSH connection despite the fact that an SSH option was modified, which should have prevented reuse. libcurl maintains a pool of previously used connections to reuse them for subsequent transfers if the configurations match. However, two SSH settings were omitted from the configuration check, allowing them to match easily, potentially leading to the reuse of an inappropriate connection. |
Affected by 19 other vulnerabilities. |
|
VCID-j1a6-7226-ebd5
Aliases: CVE-2014-0015 |
Affected by 87 other vulnerabilities. |
|
|
VCID-jb7y-7s8j-hug4
Aliases: CVE-2013-1944 |
Affected by 78 other vulnerabilities. |
|
|
VCID-kgqf-t8vs-wkbp
Aliases: CVE-2016-8619 |
The function `read_data()` in security.c in curl before version 7.51.0 is vulnerable to memory double free. |
Affected by 63 other vulnerabilities. |
|
VCID-kng1-n79f-8uhe
Aliases: CVE-2021-22924 |
libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse, if one of them matches the setup.Due to errors in the logic, the config matching function did not take 'issuercert' into account and it compared the involved paths *case insensitively*,which could lead to libcurl reusing wrong connections.File paths are, or can be, case sensitive on many systems but not all, and caneven vary depending on used file systems.The comparison also didn't include the 'issuer cert' which a transfer can setto qualify how to verify the server certificate. |
Affected by 41 other vulnerabilities. |
|
VCID-ksnr-v863-xuf1
Aliases: CVE-2011-3389 |
Affected by 72 other vulnerabilities. |
|
|
VCID-kxcf-6r7j-afge
Aliases: CVE-2020-8284 |
Affected by 43 other vulnerabilities. |
|
|
VCID-m1uj-dxcq-quf1
Aliases: CVE-2011-2192 |
Affected by 72 other vulnerabilities. |
|
|
VCID-prgz-2eea-47du
Aliases: CVE-2015-3153 |
Affected by 81 other vulnerabilities. |
|
|
VCID-prr8-xszv-87bg
Aliases: CVE-2016-7167 |
Affected by 74 other vulnerabilities. |
|
|
VCID-qgr5-ua84-cqf3
Aliases: CVE-2023-27533 |
A vulnerability in input validation exists in curl <8.0 during communication using the TELNET protocol may allow an attacker to pass on maliciously crafted user name and "telnet options" during server negotiation. The lack of proper input scrubbing allows an attacker to send content or perform option negotiation without the application's intent. This vulnerability could be exploited if an application allows user input, thereby enabling attackers to execute arbitrary code on the system. |
Affected by 19 other vulnerabilities. |
|
VCID-qshs-bp9m-wyg5
Aliases: CVE-2023-38546 |
This flaw allows an attacker to insert cookies at will into a running program using libcurl, if the specific series of conditions are met. libcurl performs transfers. In its API, an application creates "easy handles" that are the individual handles for single transfers. libcurl provides a function call that duplicates en easy handle called [curl_easy_duphandle](https://curl.se/libcurl/c/curl_easy_duphandle.html). If a transfer has cookies enabled when the handle is duplicated, the cookie-enable state is also cloned - but without cloning the actual cookies. If the source handle did not read any cookies from a specific file on disk, the cloned version of the handle would instead store the file name as `none` (using the four ASCII letters, no quotes). Subsequent use of the cloned handle that does not explicitly set a source to load cookies from would then inadvertently load cookies from a file named `none` - if such a file exists and is readable in the current directory of the program using libcurl. And if using the correct file format of course. |
Affected by 12 other vulnerabilities. |
|
VCID-r47x-jtx4-akfm
Aliases: CVE-2022-32221 |
When doing HTTP(S) transfers, libcurl might erroneously use the read callback (`CURLOPT_READFUNCTION`) to ask for data to send, even when the `CURLOPT_POSTFIELDS` option has been set, if the same handle previously was used to issue a `PUT` request which used that callback. This flaw may surprise the application and cause it to misbehave and either send off the wrong data or use memory after free or similar in the subsequent `POST` request. The problem exists in the logic for a reused handle when it is changed from a PUT to a POST. |
Affected by 29 other vulnerabilities. |
|
VCID-rbgk-zqkz-zbhb
Aliases: CVE-2022-27774 |
An insufficiently protected credentials vulnerability exists in curl 4.9 to and include curl 7.82.0 are affected that could allow an attacker to extract credentials when follows HTTP(S) redirects is used with authentication could leak credentials to other services that exist on different protocols or port numbers. |
Affected by 39 other vulnerabilities. |
|
VCID-rcux-u2gs-muaj
Aliases: CVE-2022-43552 |
A use after free vulnerability exists in curl <7.87.0. Curl can be asked to *tunnel* virtually all protocols it supports through an HTTP proxy. HTTP proxies can (and often do) deny such tunnel operations. When getting denied to tunnel the specific protocols SMB or TELNET, curl would use a heap-allocated struct after it had been freed, in its transfer shutdown code path. |
Affected by 27 other vulnerabilities. |
|
VCID-szwk-ndws-cfgp
Aliases: CVE-2016-0755 |
Affected by 80 other vulnerabilities. |
|
|
VCID-tcgy-p1fh-73a2
Aliases: CVE-2021-22925 |
curl supports the `-t` command line option, known as `CURLOPT_TELNETOPTIONS`in libcurl. This rarely used option is used to send variable=content pairs toTELNET servers.Due to flaw in the option parser for sending `NEW_ENV` variables, libcurlcould be made to pass on uninitialized data from a stack based buffer to theserver. Therefore potentially revealing sensitive internal information to theserver using a clear-text network protocol.This could happen because curl did not call and use sscanf() correctly whenparsing the string provided by the application. |
Affected by 41 other vulnerabilities. |
|
VCID-thvp-m8ct-sfbz
Aliases: CVE-2010-0734 |
Affected by 69 other vulnerabilities. |
|
|
VCID-tj1j-bpq4-2fau
Aliases: CVE-2018-1000007 |
libcurl 7.1 through 7.57.0 might accidentally leak authentication data to third parties. When asked to send custom headers in its HTTP requests, libcurl will send that set of headers first to the host in the initial URL but also, if asked to follow redirects and a 30X HTTP response code is returned, to the host mentioned in URL in the `Location:` response header value. Sending the same set of headers to subsequent hosts is in particular a problem for applications that pass on custom `Authorization:` headers, as this header often contains privacy sensitive information or data that could allow others to impersonate the libcurl-using client's request. |
Affected by 56 other vulnerabilities. |
|
VCID-tsyn-uzsk-9ke6
Aliases: CVE-2014-3613 |
Affected by 85 other vulnerabilities. |
|
|
VCID-u5gc-vvmc-augw
Aliases: CVE-2015-3143 |
Affected by 82 other vulnerabilities. |
|
|
VCID-uv1g-n7b4-y3eq
Aliases: CVE-2014-8150 |
Affected by 84 other vulnerabilities. |
|
|
VCID-vedv-nete-bfeg
Aliases: CVE-2016-5420 |
Affected by 76 other vulnerabilities. |
|
|
VCID-vkf1-a88h-6fbu
Aliases: CVE-2017-1000254 |
Affected by 60 other vulnerabilities. |
|
|
VCID-vyre-1jrv-rqea
Aliases: CVE-2025-0725 |
When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the `CURLOPT_ACCEPT_ENCODING` option, **using zlib 1.2.0.3 or older**, an attacker-controlled integer overflow would make libcurl perform a buffer overflow. |
Affected by 4 other vulnerabilities. |
|
VCID-waah-usbn-33cq
Aliases: CVE-2016-5419 |
Affected by 76 other vulnerabilities. |
|
|
VCID-wyw5-k1mb-u7h8
Aliases: CVE-2016-8615 |
A flaw was found in curl before version 7.51. If cookie state is written into a cookie jar file that is later read back and used for subsequent requests, a malicious HTTP server can inject new cookies for arbitrary domains into said cookie jar. |
Affected by 63 other vulnerabilities. |
|
VCID-x25w-g1xm-uqcm
Aliases: CVE-2022-27782 |
libcurl would reuse a previously created connection even when a TLS or SSHrelated option had been changed that should have prohibited reuse.libcurl keeps previously used connections in a connection pool for subsequenttransfers to reuse if one of them matches the setup. However, several TLS andSSH settings were left out from the configuration match checks, making themmatch too easily. |
Affected by 33 other vulnerabilities. |
|
VCID-x457-pbfh-77hd
Aliases: CVE-2009-2417 |
Affected by 62 other vulnerabilities. |
|
|
VCID-y4ws-1ba4-qkhj
Aliases: CVE-2021-22898 |
curl 7.7 through 7.76.1 suffers from an information disclosure when the `-t` command line option, known as `CURLOPT_TELNETOPTIONS` in libcurl, is used to send variable=content pairs to TELNET servers. Due to a flaw in the option parser for sending NEW_ENV variables, libcurl could be made to pass on uninitialized data from a stack based buffer to the server, resulting in potentially revealing sensitive internal information to the server using a clear-text network protocol. |
Affected by 46 other vulnerabilities. |
|
VCID-ybxb-2par-s7e8
Aliases: CVE-2016-8625 |
curl before version 7.51.0 uses outdated IDNA 2003 standard to handle International Domain Names and this may lead users to potentially and unknowingly issue network transfer requests to the wrong host. |
Affected by 63 other vulnerabilities. |
|
VCID-z2kk-kdaa-ckbh
Aliases: CVE-2022-35252 |
When curl is used to retrieve and parse cookies from a HTTP(S) server, itaccepts cookies using control codes that when later are sent back to a HTTPserver might make the server return 400 responses. Effectively allowing a"sister site" to deny service to all siblings. |
Affected by 32 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||
| Date | Actor | Action | Vulnerability | Source | VulnerableCode Version |
|---|---|---|---|---|---|
| 2025-07-31T09:35:03.114455+00:00 | Curl Importer | Affected by | VCID-7g8x-2u49-myfk | https://curl.se/docs/CVE-2009-0037.json | 37.0.0 |
| 2025-07-31T09:35:02.675915+00:00 | Curl Importer | Affected by | VCID-x457-pbfh-77hd | https://curl.se/docs/CVE-2009-2417.json | 37.0.0 |
| 2025-07-31T09:35:02.305038+00:00 | Curl Importer | Affected by | VCID-thvp-m8ct-sfbz | https://curl.se/docs/CVE-2010-0734.json | 37.0.0 |
| 2025-07-31T09:35:01.982688+00:00 | Curl Importer | Affected by | VCID-m1uj-dxcq-quf1 | https://curl.se/docs/CVE-2011-2192.json | 37.0.0 |
| 2025-07-31T09:35:01.599302+00:00 | Curl Importer | Affected by | VCID-ksnr-v863-xuf1 | https://curl.se/docs/CVE-2011-3389.json | 37.0.0 |
| 2025-07-31T09:35:01.232720+00:00 | Curl Importer | Affected by | VCID-jb7y-7s8j-hug4 | https://curl.se/docs/CVE-2013-1944.json | 37.0.0 |
| 2025-07-31T09:35:00.608625+00:00 | Curl Importer | Affected by | VCID-cf1z-1bxk-r7hs | https://curl.se/docs/CVE-2013-2174.json | 37.0.0 |
| 2025-07-31T09:34:59.861120+00:00 | Curl Importer | Affected by | VCID-j1a6-7226-ebd5 | https://curl.se/docs/CVE-2014-0015.json | 37.0.0 |
| 2025-07-31T09:34:59.506256+00:00 | Curl Importer | Affected by | VCID-3j31-rzu1-dkc9 | https://curl.se/docs/CVE-2014-0138.json | 37.0.0 |
| 2025-07-31T09:34:59.153479+00:00 | Curl Importer | Affected by | VCID-67tv-9g7a-eqhe | https://curl.se/docs/CVE-2014-0139.json | 37.0.0 |
| 2025-07-31T09:34:58.612023+00:00 | Curl Importer | Affected by | VCID-tsyn-uzsk-9ke6 | https://curl.se/docs/CVE-2014-3613.json | 37.0.0 |
| 2025-07-31T09:34:57.561090+00:00 | Curl Importer | Affected by | VCID-uv1g-n7b4-y3eq | https://curl.se/docs/CVE-2014-8150.json | 37.0.0 |
| 2025-07-31T09:34:56.873360+00:00 | Curl Importer | Affected by | VCID-u5gc-vvmc-augw | https://curl.se/docs/CVE-2015-3143.json | 37.0.0 |
| 2025-07-31T09:34:56.481831+00:00 | Curl Importer | Affected by | VCID-bmc9-d3cf-nfc4 | https://curl.se/docs/CVE-2015-3148.json | 37.0.0 |
| 2025-07-31T09:34:55.943356+00:00 | Curl Importer | Affected by | VCID-prgz-2eea-47du | https://curl.se/docs/CVE-2015-3153.json | 37.0.0 |
| 2025-07-31T09:34:55.044153+00:00 | Curl Importer | Affected by | VCID-szwk-ndws-cfgp | https://curl.se/docs/CVE-2016-0755.json | 37.0.0 |
| 2025-07-31T09:34:54.618016+00:00 | Curl Importer | Affected by | VCID-9ebs-w43b-h7as | https://curl.se/docs/CVE-2016-0754.json | 37.0.0 |
| 2025-07-31T09:34:53.540219+00:00 | Curl Importer | Affected by | VCID-7958-m7nd-tuet | https://curl.se/docs/CVE-2016-4802.json | 37.0.0 |
| 2025-07-31T09:34:52.967347+00:00 | Curl Importer | Affected by | VCID-vedv-nete-bfeg | https://curl.se/docs/CVE-2016-5420.json | 37.0.0 |
| 2025-07-31T09:34:52.417473+00:00 | Curl Importer | Affected by | VCID-waah-usbn-33cq | https://curl.se/docs/CVE-2016-5419.json | 37.0.0 |
| 2025-07-31T09:34:51.374207+00:00 | Curl Importer | Affected by | VCID-prr8-xszv-87bg | https://curl.se/docs/CVE-2016-7167.json | 37.0.0 |
| 2025-07-31T09:34:50.910728+00:00 | Curl Importer | Affected by | VCID-ybxb-2par-s7e8 | https://curl.se/docs/CVE-2016-8625.json | 37.0.0 |
| 2025-07-31T09:34:50.459139+00:00 | Curl Importer | Affected by | VCID-6g4s-g758-gyek | https://curl.se/docs/CVE-2016-8624.json | 37.0.0 |
| 2025-07-31T09:34:49.768656+00:00 | Curl Importer | Affected by | VCID-bfvw-myxs-u7fn | https://curl.se/docs/CVE-2016-8623.json | 37.0.0 |
| 2025-07-31T09:34:49.101352+00:00 | Curl Importer | Affected by | VCID-7c3e-97qs-ube7 | https://curl.se/docs/CVE-2016-8621.json | 37.0.0 |
| 2025-07-31T09:34:48.530957+00:00 | Curl Importer | Affected by | VCID-kgqf-t8vs-wkbp | https://curl.se/docs/CVE-2016-8619.json | 37.0.0 |
| 2025-07-31T09:34:47.917499+00:00 | Curl Importer | Affected by | VCID-dt8u-p2t3-mbfv | https://curl.se/docs/CVE-2016-8618.json | 37.0.0 |
| 2025-07-31T09:34:47.196368+00:00 | Curl Importer | Affected by | VCID-3pz4-p8n7-mfe7 | https://curl.se/docs/CVE-2016-8617.json | 37.0.0 |
| 2025-07-31T09:34:46.643452+00:00 | Curl Importer | Affected by | VCID-a3bj-tpnb-ekc8 | https://curl.se/docs/CVE-2016-8616.json | 37.0.0 |
| 2025-07-31T09:34:46.067697+00:00 | Curl Importer | Affected by | VCID-wyw5-k1mb-u7h8 | https://curl.se/docs/CVE-2016-8615.json | 37.0.0 |
| 2025-07-31T09:34:44.878160+00:00 | Curl Importer | Affected by | VCID-d5k5-2r4p-tqat | https://curl.se/docs/CVE-2016-9586.json | 37.0.0 |
| 2025-07-31T09:34:44.032275+00:00 | Curl Importer | Affected by | VCID-9tk9-a11p-r7fb | https://curl.se/docs/CVE-2017-7407.json | 37.0.0 |
| 2025-07-31T09:34:43.205091+00:00 | Curl Importer | Affected by | VCID-ae2d-dcng-pfe9 | https://curl.se/docs/CVE-2017-1000100.json | 37.0.0 |
| 2025-07-31T09:34:42.569574+00:00 | Curl Importer | Affected by | VCID-vkf1-a88h-6fbu | https://curl.se/docs/CVE-2017-1000254.json | 37.0.0 |
| 2025-07-31T09:34:40.925319+00:00 | Curl Importer | Affected by | VCID-tj1j-bpq4-2fau | https://curl.se/docs/CVE-2018-1000007.json | 37.0.0 |
| 2025-07-31T09:34:40.139589+00:00 | Curl Importer | Affected by | VCID-3hax-q2kc-eye5 | https://curl.se/docs/CVE-2018-1000120.json | 37.0.0 |
| 2025-07-31T09:34:38.450833+00:00 | Curl Importer | Affected by | VCID-1bg9-85q6-bya3 | https://curl.se/docs/CVE-2018-14618.json | 37.0.0 |
| 2025-07-31T09:34:37.674789+00:00 | Curl Importer | Affected by | VCID-9n9j-kk6t-jfdw | https://curl.se/docs/CVE-2018-16842.json | 37.0.0 |
| 2025-07-31T09:34:34.194138+00:00 | Curl Importer | Affected by | VCID-kxcf-6r7j-afge | https://curl.se/docs/CVE-2020-8284.json | 37.0.0 |
| 2025-07-31T09:34:32.413349+00:00 | Curl Importer | Affected by | VCID-fnu8-rhf3-9uat | https://curl.se/docs/CVE-2021-22876.json | 37.0.0 |
| 2025-07-31T09:34:31.308097+00:00 | Curl Importer | Affected by | VCID-y4ws-1ba4-qkhj | https://curl.se/docs/CVE-2021-22898.json | 37.0.0 |
| 2025-07-31T09:34:29.643228+00:00 | Curl Importer | Affected by | VCID-kng1-n79f-8uhe | https://curl.se/docs/CVE-2021-22924.json | 37.0.0 |
| 2025-07-31T09:34:28.960005+00:00 | Curl Importer | Affected by | VCID-tcgy-p1fh-73a2 | https://curl.se/docs/CVE-2021-22925.json | 37.0.0 |
| 2025-07-31T09:34:26.344513+00:00 | Curl Importer | Affected by | VCID-rbgk-zqkz-zbhb | https://curl.se/docs/CVE-2022-27774.json | 37.0.0 |
| 2025-07-31T09:34:25.169256+00:00 | Curl Importer | Affected by | VCID-7cxc-5tec-g3gm | https://curl.se/docs/CVE-2022-27776.json | 37.0.0 |
| 2025-07-31T09:34:23.617231+00:00 | Curl Importer | Affected by | VCID-x25w-g1xm-uqcm | https://curl.se/docs/CVE-2022-27782.json | 37.0.0 |
| 2025-07-31T09:34:22.506657+00:00 | Curl Importer | Affected by | VCID-7b6t-h7w2-a7am | https://curl.se/docs/CVE-2022-32208.json | 37.0.0 |
| 2025-07-31T09:34:21.896610+00:00 | Curl Importer | Affected by | VCID-z2kk-kdaa-ckbh | https://curl.se/docs/CVE-2022-35252.json | 37.0.0 |
| 2025-07-31T09:34:20.827615+00:00 | Curl Importer | Affected by | VCID-r47x-jtx4-akfm | https://curl.se/docs/CVE-2022-32221.json | 37.0.0 |
| 2025-07-31T09:34:19.684472+00:00 | Curl Importer | Affected by | VCID-rcux-u2gs-muaj | https://curl.se/docs/CVE-2022-43552.json | 37.0.0 |
| 2025-07-31T09:34:18.591409+00:00 | Curl Importer | Affected by | VCID-qgr5-ua84-cqf3 | https://curl.se/docs/CVE-2023-27533.json | 37.0.0 |
| 2025-07-31T09:34:17.098849+00:00 | Curl Importer | Affected by | VCID-4mdh-6sq4-vqfc | https://curl.se/docs/CVE-2023-27535.json | 37.0.0 |
| 2025-07-31T09:34:15.844501+00:00 | Curl Importer | Affected by | VCID-g7m2-cu4w-abes | https://curl.se/docs/CVE-2023-27538.json | 37.0.0 |
| 2025-07-31T09:34:15.080946+00:00 | Curl Importer | Affected by | VCID-dw2d-6fkr-87g2 | https://curl.se/docs/CVE-2023-28320.json | 37.0.0 |
| 2025-07-31T09:34:14.265509+00:00 | Curl Importer | Affected by | VCID-a63f-dgdt-qkeu | https://curl.se/docs/CVE-2023-28321.json | 37.0.0 |
| 2025-07-31T09:34:13.536973+00:00 | Curl Importer | Affected by | VCID-b3n4-qjn2-x7dx | https://curl.se/docs/CVE-2023-28322.json | 37.0.0 |
| 2025-07-31T09:34:12.330292+00:00 | Curl Importer | Affected by | VCID-qshs-bp9m-wyg5 | https://curl.se/docs/CVE-2023-38546.json | 37.0.0 |
| 2025-07-31T09:34:08.333222+00:00 | Curl Importer | Affected by | VCID-vyre-1jrv-rqea | https://curl.se/docs/CVE-2025-0725.json | 37.0.0 |