Re: bug in Lynx' SSL certificate validation -> leaks password in clear text via SNI (under some circumstances)
Carlo Strub <[email protected]>
| Newsgroups | gmane.os.freebsd.security.general |
|---|---|
| Message-ID | <CABSZnjPp40QEKEFwefw9XyAm81cve3hcirwBSDHANoDjrcMERw@mail.gmail.com> |
Thanks a lot for your email. I added a vuxml entry to inform users. Best, Carlo On Sat, 7 Aug 2021 at 17:07, Katherine Mcmillan <[email protected]> wrote: > FYI > > ________________________________ > From: Lynx-dev <[email protected]> on > behalf of Ariadne Conill <[email protected]> > Sent: 07 August 2021 10:17 > To: [email protected] <[email protected]> > Cc: Axel Beckert <[email protected]>; [email protected] < > [email protected]>; [email protected] <[email protected]>; > [email protected] <[email protected]> > Subject: Re: [Lynx-dev] [oss-security] Re: bug in Lynx' SSL certificate > validation -> leaks password in clear text via SNI (under some > circumstances) > > Attention : courriel externe | external email > > Hi, > > On Sat, 7 Aug 2021, Thorsten Glaser wrote: > > > Axel Beckert dixit: > > > >> This is more severe than it initially looked like: Due to TLS Server > >> Name Indication (SNI) the hostname as parsed by Lynx (i.e with > >> "user:pass@" included) is sent in _clear_ text over the wire even > > > > I *ALWAYS* SAID SNI IS A SHIT THING ONLY USED AS BAD EXCUSE FOR NAT > > BY PEOPLE WHO ARE TOO STUPID TO CONFIGURE THEIR SERVERS RIGHT AND AS > > BAD EXCUSE FOR LACKING IPv6 SUPPORT, AND THEN THE FUCKING IDIOTS WENT > > AND MADE SNI *MANDATORY* FOR TLSv1.3, AND I FEEL *SO* VINDICATED RIGHT > > NOW! IDIOTS IN CHARGE OF SECURITY, FUCKING IDIOTS… > > It turns out SNI is only marginally related to this issue. The issue > itself is far more severe: HTParse() does not understand the authn part of > the URI at all. And so, when you call: > > HTParse("https://foo:[email protected]", "", PARSE_HOST) > > It returns: > > foo:[email protected] > > Which is then handed directly to SSL_set_tlsext_host_name() or > gnutls_server_name_set(). But it will also leak in the Host: header on > unencrypted connections, and also probably SSL ones too. > > As a workaround, I taught HTParse() how to parse the authn part of URIs, > but Lynx itself needs to actually properly support the authn part really. > > I have attached the patch Alpine is using to work around this infoleak. > > Ariadne > _______________________________________________ > [email protected] mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to "[email protected] > " > _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-security To unsubscribe, send any mail to "[email protected]"