From: Jeffrey E Altman <jaltman@auristor.com>
To: Kenny Ho <y2kenny@gmail.com>, David Laight <David.Laight@aculab.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Marc Dionne <marc.dionne@auristor.com>,
Kenny Ho <Kenny.Ho@amd.com>, David Howells <dhowells@redhat.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"linux-afs@lists.infradead.org" <linux-afs@lists.infradead.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove hardcoded static string length
Date: Sat, 27 May 2023 11:08:58 -0400 [thread overview]
Message-ID: <c22f76b1-0559-410f-38f2-266e1a9fcca5@auristor.com> (raw)
In-Reply-To: <CAOWid-d=OFn7JS5JvsK9qc7X6HeZgOm5OAd1_g2=_GZgpKRZnA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2020 bytes --]
On 5/25/2023 11:37 AM, Kenny Ho wrote:
> On Thu, May 25, 2023 at 11:04 AM David Laight<David.Laight@aculab.com> wrote:
>>> "The standard formulation seems to be: <project> <version> built
>>> <yyyy>-<mm>-<dd>"
>> Which I don't recall the string actually matching?
>> Also the people who like reproducible builds don't like __DATE__.
> That's correct, it was not matching even when it was introduced. I am
> simply taking that as people caring about the content and not simply
> making rxrpc_version_string == UTS_RELEASE. The current format is:
>
> "linux-" UTS_RELEASE " AF_RXRPC"
>
> Kenny
The RX_PACKET_TYPE_VERSION query is issued by the "rxdebug <host> <port>
-version" command which prints the received string to stdout. It has
also been used some implementations to record the version of the peer.
Although it is required that a response to the RX_PACKET_TYPE_VERSION
query be issued, there is no requirement that the returned string
contain anything beyond a single NUL octet.
Although it is convenient to be able to remotely identify the version of
an Rx implementation, there are good reasons why this information should
not be exposed to an anonymous requester:
1. Linux AF_RXRPC is part of the kernel. As such, returning
UTS_RELEASE identifies to potential attackers the explicit kernel
version, architecture and perhaps distro. As this query can be
issued anonymously, this provides an information disclosure that can
be used to target known vulnerabilities in the kernel.
2. The RX_PACKET_TYPE_VERSION reply is larger than the query by the
number of octets in the version data. As the query is received via
udp with no reachability test, it means that the
RX_PACKET_TYPE_VERSION query/response can be used to perform an 3.3x
amplification attack: 28 octets in and potentially 93 octets out.
With my security hat on I would suggest that either AF_RXRPC return a
single NUL octet or the c-string "AF_RXRPC" and nothing more.
Jeffrey Altman
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4039 bytes --]
next prev parent reply other threads:[~2023-05-27 15:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 22:39 Kenny Ho
2023-05-24 0:49 ` Andrew Lunn
2023-05-24 15:43 ` Marc Dionne
2023-05-24 16:01 ` Andrew Lunn
2023-05-24 17:02 ` Kenny Ho
2023-05-24 17:43 ` Andrew Lunn
2023-05-24 18:01 ` Kenny Ho
2023-05-25 9:14 ` David Laight
2023-05-25 14:27 ` Kenny Ho
2023-05-25 15:04 ` David Laight
2023-05-25 15:37 ` Kenny Ho
2023-05-27 15:08 ` Jeffrey E Altman [this message]
2023-05-29 13:32 ` David Laight
2023-05-30 14:39 ` Jeffrey E Altman
2023-05-27 14:45 ` Jeffrey E Altman
2023-05-27 15:08 ` Jeffrey E Altman
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=c22f76b1-0559-410f-38f2-266e1a9fcca5@auristor.com \
--to=jaltman@auristor.com \
--cc=David.Laight@aculab.com \
--cc=Kenny.Ho@amd.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=y2kenny@gmail.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
all inboxes | Powered by JetHome®