From: walter harms <wharms@bfs.de>
To: Vasiliy Kulikov <segooon@gmail.com>
Cc: kernel-janitors@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Jiri Pirko <jpirko@redhat.com>,
Eric Dumazet <eric.dumazet@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] net: packet: fix information leak to userland
Date: Sun, 07 Nov 2010 12:56:18 +0000 [thread overview]
Message-ID: <4CD6A1F2.9040301@bfs.de> (raw)
In-Reply-To: <20101107120636.GA7101@albatros>
Am 07.11.2010 13:06, schrieb Vasiliy Kulikov:
> On Sun, Nov 07, 2010 at 12:37 +0100, walter harms wrote:
>> Am 06.11.2010 15:39, schrieb Vasiliy Kulikov:
>>> On Mon, Nov 01, 2010 at 10:14 +0100, walter harms wrote:
>>>> Vasiliy Kulikov schrieb:
>>>>> @@ -1719,7 +1719,7 @@ static int packet_getname_spkt(struct socket *sock, struct sockaddr *uaddr,
>>>>> rcu_read_lock();
>>>>> dev = dev_get_by_index_rcu(sock_net(sk), pkt_sk(sk)->ifindex);
>>>>> if (dev)
>>>>> - strlcpy(uaddr->sa_data, dev->name, 15);
>>>>> + strncpy(uaddr->sa_data, dev->name, 14);
>>>>> else
>>>>> memset(uaddr->sa_data, 0, 14);
>>>>
>>>> if i understand the code correcly the max size for dev->name is IFNAMSIZ.
>>>
>>> For dev->name - IFNAMSIZ, for uaddr->sa_data - 14.
>>>
>>
>>
>> did not notice, since uaddr->sa_data should take dev->name this does no look very
>> clever. How is the size of sa_data defined ?
>
> Magic size...
>
> ~/linux/include/linux/socket.h:
>
> struct sockaddr {
> sa_family_t sa_family; /* address family, AF_xxx */
> char sa_data[14]; /* 14 bytes of protocol address */
> };
>
>
>> Would it hurt when some uses IFNAMSIZ here ?
>
so i should be more direct. the idea was :
char sa_data[IFNAMSIZ];
> If copy _to_ sa_data string of maximum IFNAMSIZ bytes - yes.
>
>
> In packet_getname_spkt() the output buffer is 128 bytes, so it doesn't
> really overflows anything. I don't think that *_getname() implementations
> don't know this.
>
>> Perhaps someone who know more about the network stack can figure out what is actualy done
>> with uaddr->sa_data.
>
> Yeah, also I wonder whether it is always NULL-terminated string or not.
>
>> looks like a can of worms.
>>
>>
>> In packet_bind_spkt() they will copy a char[15], obviously it is a real problem.
>
> No, packet_bind_spkt() copies 14-byte string into array of 15 bytes.
> The vice versa would be a bug.
>
ups your are right, wrong way around. it still does not look clever.
I have the feeling that the basic idea what to store the string with out \0.
according to this:
http://www.gnu.org/s/libc/manual/html_node/Address-Formats.html
It should work.
re,
wh
next prev parent reply other threads:[~2010-11-07 12:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-31 17:10 [PATCH 2/3] net: packet: fix information leak to userland Vasiliy Kulikov
2010-11-01 9:14 ` walter harms
2010-11-06 14:39 ` Vasiliy Kulikov
2010-11-07 11:37 ` walter harms
2010-11-07 12:06 ` Vasiliy Kulikov
2010-11-07 12:56 ` walter harms [this message]
2010-11-10 18:16 ` Vasiliy Kulikov
2010-11-10 18:20 ` David Miller
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=4CD6A1F2.9040301@bfs.de \
--to=wharms@bfs.de \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jpirko@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=segooon@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;
as well as URLs for NNTP newsgroup(s).