From: Dan Williams <dcbw@redhat.com>
To: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
"Jakub Kicinski" <kuba@kernel.org>,
"Paolo Abeni" <pabeni@redhat.com>,
"Kalle Valo" <kvalo@kernel.org>,
"Oleksij Rempel" <linux@rempel-privat.de>,
"Maciej Żenczykowski" <maze@google.com>,
"Neil Armstrong" <neil.armstrong@linaro.org>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Andrzej Pietrasiewicz" <andrzejtp2010@gmail.com>,
"Jacopo Mondi" <jacopo@jmondi.org>,
"Łukasz Stelmach" <l.stelmach@samsung.com>,
"Laurent Pinchart" <laurent.pinchart@ideasonboard.com>,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org,
"Ilja Van Sprundel" <ivansprundel@ioactive.com>,
"Joseph Tartaro" <joseph.tartaro@ioactive.com>
Subject: Re: [PATCH] USB: disable all RNDIS protocol drivers
Date: Tue, 29 Nov 2022 16:48:07 -0600 [thread overview]
Message-ID: <8b11568a8022cdb759a43f34fdcddf33d9abc37c.camel@redhat.com> (raw)
In-Reply-To: <04ea37cc-d97a-3e00-8a99-135ab38860f2@green-communications.fr>
On Wed, 2022-11-23 at 16:40 +0100, Nicolas Cavallari wrote:
> On 23/11/2022 13:46, Greg Kroah-Hartman wrote:
> > The Microsoft RNDIS protocol is, as designed, insecure and
> > vulnerable on
> > any system that uses it with untrusted hosts or devices. Because
> > the
> > protocol is impossible to make secure, just disable all rndis
> > drivers to
> > prevent anyone from using them again.
> >
> > Windows only needed this for XP and newer systems, Windows systems
> > older
> > than that can use the normal USB class protocols instead, which do
> > not
> > have these problems.
> >
> > Android has had this disabled for many years so there should not be
> > any
> > real systems that still need this.
>
> I kind of disagree here. I have seen plenty of android devices that
> only
> support rndis for connection sharing, including my android 11 phone
> released in Q3 2020. I suspect the qualcomm's BSP still enable it by
> default.
>
> There are also probably cellular dongles that uses rndis by default.
> Maybe ask the ModemManager people ?
Yes, there are.
Another class of WWAN dongles presented as USB RNDIS to the host, had
an onboard DHCP server, and "bridged" that (for lack of a better term)
to the WWAN. And like a home router exposed HTTP based management on
192.168.1.1 to control the WWAN stuff.
https://openwrt.org/docs/guide-user/network/wan/wwan/ethernetoverusb_rndis
RE Wifi, (echoing Johannes) there was one Broadcom chipset, but a bunch
of devices used it. I have some though I don't actively use them. But
they still work...
Dan
>
> I'm also curious if reimplementing it in userspace would solve the
> security problem.
>
next prev parent reply other threads:[~2022-11-29 22:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 15:40 [PATCH] USB: disable all RNDIS protocol drivers Nicolas Cavallari
2022-11-23 15:55 ` Greg Kroah-Hartman
2022-11-24 0:58 ` Lars Melin
2022-11-29 22:48 ` Dan Williams [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-23 12:46 Greg Kroah-Hartman
2022-11-23 14:20 ` Johannes Berg
2022-11-23 15:05 ` Greg Kroah-Hartman
2022-11-23 16:27 ` Johannes Berg
2023-01-10 22:47 ` James Hilliard
2022-11-23 15:21 ` Kalle Valo
2022-11-23 18:29 ` Jakub Kicinski
2022-11-23 20:27 ` Maciej Żenczykowski
2023-01-11 13:38 ` Jan Engelhardt
2023-01-11 14:56 ` Greg Kroah-Hartman
2023-07-03 21:11 ` Enrico Mioso
2023-07-04 6:47 ` Greg Kroah-Hartman
2023-07-12 9:22 ` Oliver Neukum
2023-07-12 13:00 ` Johannes Berg
2023-07-12 16:39 ` Greg Kroah-Hartman
2023-07-13 0:28 ` Johannes Berg
2023-07-13 5:34 ` Greg Kroah-Hartman
2023-07-13 8:33 ` Oliver Neukum
2023-07-13 9:49 ` Maciej Żenczykowski
2023-07-13 12:21 ` Johannes Berg
2023-07-13 5:21 ` Mauro Carvalho Chehab
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8b11568a8022cdb759a43f34fdcddf33d9abc37c.camel@redhat.com \
--to=dcbw@redhat.com \
--cc=andrzejtp2010@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=ivansprundel@ioactive.com \
--cc=jacopo@jmondi.org \
--cc=joseph.tartaro@ioactive.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=l.stelmach@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=maze@google.com \
--cc=mchehab@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=netdev@vger.kernel.org \
--cc=nicolas.cavallari@green-communications.fr \
--cc=pabeni@redhat.com \
/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.
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 NNTP newsgroup(s).