From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Cyrill Gorcunov" <gorcunov@gmail.com>
Cc: "Tom Tucker" <tom@opengridcomputing.com>,
"Neil Brown" <neilb@suse.de>,
"Chuck Lever" <chuck.lever@oracle.com>,
"Greg Banks" <gnb@sgi.com>,
"J. Bruce Fields" <bfields@citi.umich.edu>,
linux-kernel@vger.kernel.org
Subject: Re: buffer overflow in /proc/sys/sunrpc/transports
Date: Sat, 30 Aug 2008 21:15:16 +0200 [thread overview]
Message-ID: <19f34abd0808301215i445e8411q987c864c0b478d30@mail.gmail.com> (raw)
In-Reply-To: <20080830190642.GC7611@lenovo>
On Sat, Aug 30, 2008 at 9:06 PM, Cyrill Gorcunov <gorcunov@gmail.com> wrote:
> [Vegard Nossum - Sat, Aug 30, 2008 at 08:44:22PM +0200]
> | Hi,
> |
> | I noticed that something weird is going on with /proc/sys/sunrpc/transports.
> | This file is generated in net/sunrpc/sysctl.c, function proc_do_xprt(). When
> | I "cat" this file, I get the expected output:
> |
> | $ cat /proc/sys/sunrpc/transports
> | tcp 1048576
> | udp 32768
> |
> | But I think that it does not check the length of the buffer supplied by
> | userspace to read(). With my original program, I found that the stack was
> | being overwritten by the characters above, even when the length given to
> | read() was just 1. So I have created a test program, see it at the bottom of
> | this e-mail. Here is its output:
> |
> ...
>
> Indeed, maybe just add checking for user buffer length?
> As proc_dodebug() in this file are doing. I don't think
> the user would be happy with his stack burned :)
>
> Something like:
> ---
>
> Index: linux-2.6.git/net/sunrpc/sysctl.c
> ===================================================================
> --- linux-2.6.git.orig/net/sunrpc/sysctl.c 2008-07-20 11:40:14.000000000 +0400
> +++ linux-2.6.git/net/sunrpc/sysctl.c 2008-08-30 23:05:30.000000000 +0400
> @@ -69,6 +69,8 @@ static int proc_do_xprt(ctl_table *table
> return -EINVAL;
> else {
> len = svc_print_xprts(tmpbuf, sizeof(tmpbuf));
> + if (*lenp < len)
> + return -EFAULT;
> if (!access_ok(VERIFY_WRITE, buffer, len))
> return -EFAULT;
>
Hm. I think this is wrong. Shouldn't we copy as many bytes as the user
indicated?
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
next prev parent reply other threads:[~2008-08-30 19:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-30 18:44 Vegard Nossum
2008-08-30 19:06 ` Cyrill Gorcunov
2008-08-30 19:15 ` Vegard Nossum [this message]
2008-08-30 19:21 ` Cyrill Gorcunov
2008-08-30 19:23 ` Cyrill Gorcunov
2008-08-30 19:34 ` Vegard Nossum
2008-08-30 19:44 ` Cyrill Gorcunov
2008-08-30 19:42 ` Vegard Nossum
2008-08-30 19:45 ` Cyrill Gorcunov
2008-08-30 19:56 ` Cyrill Gorcunov
2008-08-30 19:59 ` Vegard Nossum
2008-08-30 20:04 ` Cyrill Gorcunov
2008-08-30 20:13 ` Vegard Nossum
2008-08-30 20:15 ` Cyrill Gorcunov
2008-08-30 20:29 ` Cyrill Gorcunov
2008-08-30 22:55 ` David Wagner
2008-08-31 8:37 ` Cyrill Gorcunov
2008-08-31 10:30 ` Cyrill Gorcunov
2008-08-31 10:37 ` Cyrill Gorcunov
2008-08-30 20:20 ` David Wagner
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=19f34abd0808301215i445e8411q987c864c0b478d30@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=bfields@citi.umich.edu \
--cc=chuck.lever@oracle.com \
--cc=gnb@sgi.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tom@opengridcomputing.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®