From: Andres Salomon <dilinger@debian.org>
To: dann frazier <dannf@hp.com>
Cc: linux-kernel@vger.kernel.org, Jiri Slaby <jirislaby@gmail.com>,
support@moxa.com.tw
Subject: Re: old buffer overflow in moxa driver
Date: Tue, 01 May 2007 00:05:59 -0400 [thread overview]
Message-ID: <4636BCA7.2090301@debian.org> (raw)
In-Reply-To: <20070430224829.GI31283@krebs.dannf>
Wow, I'd forgotten all about this one.
Signed-off-by: Andres Salomon <dilinger@debian.org>
dann frazier wrote:
> hey,
> 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.
>
> I've tested that this still applies to and compiles against 2.6.21.
>
> Signed-off-by: dann frazier <dannf@hp.com>
>
> diff --git a/drivers/char/moxa.c b/drivers/char/moxa.c
> index 7dbaee8..e0d35c2 100644
> --- a/drivers/char/moxa.c
> +++ b/drivers/char/moxa.c
> @@ -1582,7 +1582,7 @@ copy:
>
> if(copy_from_user(&dltmp, argp, sizeof(struct dl_str)))
> return -EFAULT;
> - if(dltmp.cardno < 0 || dltmp.cardno >= MAX_BOARDS)
> + if(dltmp.cardno < 0 || dltmp.cardno >= MAX_BOARDS || dltmp.len < 0)
> return -EINVAL;
>
> switch(cmd)
> @@ -2529,6 +2529,8 @@ static int moxaloadbios(int cardno, unsigned char __user *tmp, int len)
> void __iomem *baseAddr;
> int i;
>
> + if(len < 0 || len > sizeof(moxaBuff))
> + return -EINVAL;
> if(copy_from_user(moxaBuff, tmp, len))
> return -EFAULT;
> baseAddr = moxa_boards[cardno].basemem;
> @@ -2576,7 +2578,7 @@ static int moxaload320b(int cardno, unsigned char __user *tmp, int len)
> void __iomem *baseAddr;
> int i;
>
> - if(len > sizeof(moxaBuff))
> + if(len < 0 || len > sizeof(moxaBuff))
> return -EINVAL;
> if(copy_from_user(moxaBuff, tmp, len))
> return -EFAULT;
> @@ -2596,6 +2598,8 @@ static int moxaloadcode(int cardno, unsigned char __user *tmp, int len)
> void __iomem *baseAddr, *ofsAddr;
> int retval, port, i;
>
> + if(len < 0 || len > sizeof(moxaBuff))
> + return -EINVAL;
> if(copy_from_user(moxaBuff, tmp, len))
> return -EFAULT;
> baseAddr = moxa_boards[cardno].basemem;
>
next prev parent reply other threads:[~2007-05-01 4:35 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
2007-05-01 14:49 ` dann frazier
2007-05-01 4:05 ` Andres Salomon [this message]
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=4636BCA7.2090301@debian.org \
--to=dilinger@debian.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox