From: Alexander Viro <aviro@redhat.com>
To: Steve Grubb <sgrubb@redhat.com>
Cc: linux-audit@redhat.com, aaw@google.com, a.p.zijlstra@chello.nl
Subject: Re: [patch 058/209] audit: rework execve audit
Date: Fri, 27 Jul 2007 16:50:30 -0400 [thread overview]
Message-ID: <20070727205030.GE13539@devserv.devel.redhat.com> (raw)
In-Reply-To: <200707271613.10753.sgrubb@redhat.com>
On Fri, Jul 27, 2007 at 04:13:10PM -0400, Steve Grubb wrote:
> > + len = strnlen_user(p, MAX_ARG_PAGES*PAGE_SIZE);
> > + /*
> > + * We just created this mm, if we can't find the strings
> > + * we just copied into it something is _very_ wrong. Similar
> > + * for strings that are too long, we should not have created
> > + * any.
> > + */
> > + if (!len || len > MAX_ARG_STRLEN) {
> > + WARN_ON(1);
> > + send_sig(SIGKILL, current, 0);
> > + }
>
> Which is right here ^^^
>
> Any ideas?
Empty string in the middle of argv? Quite legal...
; cat foo.c
#include <stdio.h>
main(int argc, char **argv)
{
while (argc--) {
printf("<%d:%s>", strlen(*argv), *argv);
argv++;
}
printf("\n");
return 0;
}
; gcc foo.c
; ./a.out a b
<7:./a.out><1:a><1:b>
; ./a.out a "" b
<7:./a.out><1:a><0:><1:b>
;
IOW, it's trivial to arrange - len can be 0 just fine...
next prev parent reply other threads:[~2007-07-27 20:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 8:48 [patch 058/209] audit: rework execve audit akpm
2007-07-27 20:13 ` Steve Grubb
2007-07-27 20:44 ` Peter Zijlstra
2007-07-27 20:57 ` Steve Grubb
2007-07-27 21:55 ` Peter Zijlstra
2007-07-27 22:06 ` Peter Zijlstra
2007-07-27 22:24 ` Peter Zijlstra
2007-07-27 20:50 ` Alexander Viro [this message]
2007-07-27 21:03 ` Alexander Viro
2007-07-27 21:11 ` Steve Grubb
2007-07-27 21:21 ` Alexander Viro
2007-07-27 22:55 ` [PATCH] audit: fix two bugs in the new execve audit code Peter Zijlstra
2007-07-27 23:05 ` Andrew Morton
2007-07-28 2:05 ` Steve Grubb
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=20070727205030.GE13539@devserv.devel.redhat.com \
--to=aviro@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=aaw@google.com \
--cc=linux-audit@redhat.com \
--cc=sgrubb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.