mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Michael Buesch <mb@bu3sch.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nvram: Fix root triggerable integer overflow crash
Date: Sat, 18 Jul 2009 15:53:11 -0300	[thread overview]
Message-ID: <20090718185311.GA13198@khazad-dum.debian.net> (raw)
In-Reply-To: <200907181944.33338.mb@bu3sch.de>

On Sat, 18 Jul 2009, Michael Buesch wrote:
> On Saturday 18 July 2009 17:09:09 Henrique de Moraes Holschuh wrote:
> > On Sat, 18 Jul 2009, Michael Buesch wrote:
> > > This bug probably is exploitable by overwriting the function return address or something
> > > like that. But let's hope there's no distribution out there with user write permissions
> > > on the /dev/nvram node. So it's probably only exploitable by root.
> > 
> > I have seen setups with group-writeable /dev/nvram to support some (old!)
> > thinkpad utilities.
> 
> Yes it is  crw-rw---- 1 root root  on Debian.

That is not a problem. "crw-rw---- 1 root nvram", would be.  That becomes a
local privilege escalation right there, if it can be exploited for something
other than DoS (which looks somewhat likely).

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

      reply	other threads:[~2009-07-18 18:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-18  0:56 Michael Buesch
2009-07-18 15:09 ` Henrique de Moraes Holschuh
2009-07-18 17:44   ` Michael Buesch
2009-07-18 18:53     ` Henrique de Moraes Holschuh [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=20090718185311.GA13198@khazad-dum.debian.net \
    --to=hmh@hmh.eng.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mb@bu3sch.de \
    /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®