| CVE-2023-46219 |
BDSA-2023-3395 |
Medium |
Dec 12, 2023 |
When saving HSTS data to an excessively long file name, curl could end up
removing all contents, making subsequent requests using that file unaware of
more...
When saving HSTS data to an excessively long file name, curl could end up
removing all contents, making subsequent requests using that file unaware of
the HSTS status they should otherwise use.
less...
|
8.3.0, 8.2.0, 8.1.2, 8.1.0, 8.0.0, 7.88.1, 7.88.0
|
| CVE-2023-46218 |
BDSA-2023-3394 |
Medium |
Dec 07, 2023 |
This flaw allows a malicious HTTP server to set "super cookies" in curl that
are then passed back to more origins than what is otherwise allowed or
pos
more...
This flaw allows a malicious HTTP server to set "super cookies" in curl that
are then passed back to more origins than what is otherwise allowed or
possible. This allows a site to set cookies that then would get sent to
different and unrelated sites and domains.
It could do this by exploiting a mixed case flaw in curl's function that
verifies a given cookie domain against the Public Suffix List (PSL). For
example a cookie could be set with `domain=co.UK` when the URL used a lower
case hostname `curl.co.uk`, even though `co.uk` is listed as a PSL domain.
less...
|
8.3.0, 8.2.0, 8.1.2, 8.1.0, 8.0.0, 7.88.1, 7.88.0, 7.83.0, 7.81.0, 7.76.0
|
| CVE-2023-38546 |
BDSA-2023-2699 |
Low |
Oct 18, 2023 |
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 per
more...
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.
less...
|
8.3.0, 8.2.0, 8.1.2, 8.1.0, 8.0.0, 7.88.1, 7.88.0, 7.83.0, 7.81.0, 7.76.0
|
| CVE-2023-38545 |
BDSA-2023-2697 |
Critical |
Oct 18, 2023 |
This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy
handshake.
When curl is asked to pass along the host name to the SOCKS5 proxy to
more...
This flaw makes curl overflow a heap based buffer in the SOCKS5 proxy
handshake.
When curl is asked to pass along the host name to the SOCKS5 proxy to allow
that to resolve the address instead of it getting done by curl itself, the
maximum length that host name can be is 255 bytes.
If the host name is detected to be longer, curl switches to local name
resolving and instead passes on the resolved address only. Due to this bug,
the local variable that means "let the host resolve the name" could get the
wrong value during a slow SOCKS5 handshake, and contrary to the intention,
copy the too long host name to the target buffer instead of copying just the
resolved address there.
The target buffer being a heap based buffer, and the host name coming from the
URL that curl has been told to operate with.
less...
|
8.3.0, 8.2.0, 8.1.2, 8.1.0, 8.0.0, 7.88.1, 7.88.0, 7.83.0, 7.81.0, 7.76.0
|
