From: "David S. Miller" <davem@redhat.com>
To: kash@Stanford.EDU
Cc: linux-kernel@vger.kernel.org, mc@cs.Stanford.EDU
Subject: Re: [CHECKER] two probable security holes
Date: Mon, 24 Sep 2001 18:27:14 -0700 (PDT) [thread overview]
Message-ID: <20010924.182714.35014075.davem@redhat.com> (raw)
In-Reply-To: <Pine.GSO.4.31.0109241733010.17545-100000@myth7.Stanford.EDU>
In-Reply-To: <20010924.172608.105430357.davem@redhat.com> <Pine.GSO.4.31.0109241733010.17545-100000@myth7.Stanford.EDU>
From: Ken Ashcraft <kash@Stanford.EDU>
Date: Mon, 24 Sep 2001 17:41:44 -0700 (PDT)
It happens because the format string to a printing function is
set by the user. You are correct that ifr_name[] is not a user pointer,
but the contents of that array could contain dangerous placeholders set by
the user. I hope that clears things up.
I see... luckily these are (as far as I can tell) all root-only
operations.
Ok, it's pretty easy to add a quick verifier to dev_alloc_name, I'll
code that up.
Franks a lot,
David S. Miller
davem@redhat.com
prev parent reply other threads:[~2001-09-25 1:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-18 21:29 Ken Ashcraft
2001-09-25 0:26 ` David S. Miller
2001-09-25 0:41 ` Ken Ashcraft
2001-09-25 1:27 ` David S. Miller [this message]
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=20010924.182714.35014075.davem@redhat.com \
--to=davem@redhat.com \
--cc=kash@Stanford.EDU \
--cc=linux-kernel@vger.kernel.org \
--cc=mc@cs.Stanford.EDU \
/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®