All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andres Salomon <dilinger@debian.org>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, dann frazier <dannf@hp.com>,
	linux-kernel@vger.kernel.org, support@moxa.com.tw
Subject: Re: old buffer overflow in moxa driver
Date: Tue, 01 May 2007 04:29:27 -0400	[thread overview]
Message-ID: <4636FA67.70407@debian.org> (raw)
In-Reply-To: <4636F337.3060702@gmail.com>

Jiri Slaby wrote:
> Alan Cox napsal(a):
>>>   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.
> 
> The problem is that we BUG_ON, when len < 0 in copy_from_user which is unlikely
> something we want to cause?
> 
> regards,


Right; the lack of input checking is most definitely a bug.  It's no
longer a security issue, as a CAP_SYS_RAWIO check was added at some
point to the code path, but it's still a bug.

  reply	other threads:[~2007-05-01  8:29 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
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 [this message]
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=4636FA67.70407@debian.org \
    --to=dilinger@debian.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dannf@hp.com \
    --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 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.