From: "Léo Le Bouter via Bug reports for GNU Guix" <bug-guix@gnu.org>
To: 47563@debbugs.gnu.org
Subject: bug#47563: curl is vulnerable to CVE-2021-22890 and CVE-2021-22876
Date: Fri, 02 Apr 2021 16:04:31 +0200 [thread overview]
Message-ID: <3f93f64c692d9e0604aa406a735d81084443b692.camel@zaclys.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1416 bytes --]
CVE-2021-22890 01.04.21 20:15
curl 7.63.0 to and including 7.75.0 includes vulnerability that allows
a malicious HTTPS proxy to MITM a connection due to bad handling of TLS
1.3 session tickets. When using a HTTPS proxy and TLS 1.3, libcurl can
confuse session tickets arriving from the HTTPS proxy but work as if
they arrived from the remote server and then wrongly "short-cut" the
host handshake. When confusing the tickets, a HTTPS proxy can trick
libcurl to use the wrong session ticket resume for the host and thereby
circumvent the server TLS certificate check and make a MITM attack to
be possible to perform unnoticed. Note that such a malicious HTTPS
proxy needs to provide a certificate that curl will accept for the
MITMed server for an attack to work - unless curl has been told to
ignore the server certificate check.
CVE-2021-22876 01.04.21 20:15
curl 7.1.1 to and including 7.75.0 is vulnerable to an "Exposure of
Private Personal Information to an Unauthorized Actor" by leaking
credentials in the HTTP Referer: header. libcurl does not strip off
user credentials from the URL when automatically populating the
Referer: HTTP request header field in outgoing HTTP requests, and
therefore risks leaking sensitive data to the server that is the target
of the second HTTP request.
A WIP patch will follow, please help finishing it (rebase curl-CVE-
2021-22890.patch on 7.74.0).
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2021-04-02 14:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 14:04 Léo Le Bouter via Bug reports for GNU Guix [this message]
2021-04-02 14:09 ` bug#47563: [PATCH 0/1] gnu: curl: Fix CVE-2021-22876 and CVE-2021-22890 Léo Le Bouter via Bug reports for GNU Guix
2021-04-02 14:09 ` bug#47563: [PATCH 1/1] " Léo Le Bouter via Bug reports for GNU Guix
2021-04-02 18:22 ` bug#47563: [PATCH 0/1] " Leo Famulari
2021-04-02 18:43 ` Léo Le Bouter via Bug reports for GNU Guix
2021-04-02 19:24 ` bug#47563: [PATCH] gnu: curl: Update to 7.76.0 [security fixes] Léo Le Bouter via Bug reports for GNU Guix
2021-04-02 19:33 ` bug#47563: [PATCH v2] " Léo Le Bouter via Bug reports for GNU Guix
2021-04-02 19:34 ` Léo Le Bouter via Bug reports for GNU Guix
2021-04-02 20:36 ` Leo Famulari
2021-04-02 20:46 ` Leo Famulari
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3f93f64c692d9e0604aa406a735d81084443b692.camel@zaclys.net \
--to=bug-guix@gnu.org \
--cc=47563@debbugs.gnu.org \
--cc=lle-bout@zaclys.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).