All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: dann frazier <dannf@hp.com>,
	linux-kernel@vger.kernel.org, support@moxa.com.tw,
	dilinger@debian.org
Subject: Re: old buffer overflow in moxa driver
Date: Tue, 01 May 2007 09:58:47 +0200	[thread overview]
Message-ID: <4636F337.3060702@gmail.com> (raw)
In-Reply-To: <20070501000455.2173b1e2@the-village.bc.nu>

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,
-- 
http://www.fi.muni.cz/~xslaby/            Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8  22A0 32CC 55C3 39D4 7A7E

  parent reply	other threads:[~2007-05-01  7:58 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 [this message]
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=4636F337.3060702@gmail.com \
    --to=jirislaby@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dannf@hp.com \
    --cc=dilinger@debian.org \
    --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.