public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ismail Dönmez" <ismail@pardus.org.tr>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dann frazier <dannf@hp.com>,
	linux-kernel@vger.kernel.org, Jiri Slaby <jirislaby@gmail.com>,
	support@moxa.com.tw, dilinger@debian.org
Subject: Re: old buffer overflow in moxa driver
Date: Tue, 1 May 2007 03:01:29 +0300	[thread overview]
Message-ID: <200705010301.34571.ismail@pardus.org.tr> (raw)
In-Reply-To: <20070501000455.2173b1e2@the-village.bc.nu>

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]

On Tuesday 01 May 2007 02:04:55 Alan Cox wrote:
> >   I noticed that the moxa input checking security bug described by
> > CVE-2005-0504 appears to remain unfixed upstream.
> >
> > The issue is described here:
> >   http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2005-0504
> >
> > Debian has been shipping the following patch from Andres Salomon. I
> > tried contacting the listed maintainer a few months ago but received
> > no response.
>
>        case MOXA_LOAD_BIOS:
>         case MOXA_FIND_BOARD:
>         case MOXA_LOAD_C320B:
>         case MOXA_LOAD_CODE:
>                 if (!capable(CAP_SYS_RAWIO))
>                         return -EPERM;
>                 break;
>
> At the point you abuse these calls you can already just load arbitary
> data from userspace anyway.

So the possible exploit will only work when run by root, is that what you 
mean? If so isn't that still a security problem?

Sorry if I misunderstood what you said.

Regards,
ismail


[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2007-05-01  0:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-30 22:48 old buffer overflow in moxa driver dann frazier
2007-04-30 23:04 ` Alan Cox
2007-05-01  0:01   ` Ismail Dönmez [this message]
2007-05-01  9:52     ` Alan Cox
2007-05-01 10:03       ` Jiri Slaby
2007-05-01  7:58   ` Jiri Slaby
2007-05-01  8:29     ` Andres Salomon
2007-05-01 14:49       ` dann frazier
2007-05-01  4:05 ` Andres Salomon
2007-05-03  4:20 ` Andrew Morton

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=200705010301.34571.ismail@pardus.org.tr \
    --to=ismail@pardus.org.tr \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dannf@hp.com \
    --cc=dilinger@debian.org \
    --cc=jirislaby@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=support@moxa.com.tw \
    /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