From: Pavel Roskin <proski-mXXj517/zsQ@public.gmane.org>
To: Jouni Malinen <jkmaline-kf+aQKke1yb1KXRcyAk9cg@public.gmane.org>
Cc: orinoco-devel
<orinoco-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>,
NetDev <netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Meder Kydyraliev <meder-ljIgrh4ImVw@public.gmane.org>
Subject: Re: [PATCH SECURITY]: orinoco: Information leakage due to incorrect padding
Date: Fri, 07 Oct 2005 09:39:43 -0400 [thread overview]
Message-ID: <1128692383.13065.23.camel@dv> (raw)
In-Reply-To: <20051007032537.GB3936-mgr6C1c9aYeHXe+LvDLADg@public.gmane.org>
Hi, Jouni!
On Thu, 2005-10-06 at 20:25 -0700, Jouni Malinen wrote:
> On Tue, Oct 04, 2005 at 09:33:10PM -0400, Pavel Roskin wrote:
>
> > orinoco: Information leakage due to incorrect padding
> >
> > The orinoco driver can send uninitialized data exposing random pieces of
> > the system memory. This happens because data is not padded with zeroes
> > when its length needs to be increased.
>
> Issue itself looks valid in the current implementation, but a better fix
> would be to just remove the padding.
Thank you! With you and Jean saying that, I'm pretty much reassured
now :-)
I'll do it in Orinoco CVS soon and then I'll submit the patch.
The patch I posted is actually a simplified version of the patch
actually applied to the orinoco CVS, to make it as safe as possible for
Linux 2.6.14 inclusion.
--
Regards,
Pavel Roskin
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
prev parent reply other threads:[~2005-10-07 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 1:33 [PATCH SECURITY]: orinoco: Information leakage due to incorrect padding Pavel Roskin
2005-10-07 3:25 ` Jouni Malinen
[not found] ` <20051007032537.GB3936-mgr6C1c9aYeHXe+LvDLADg@public.gmane.org>
2005-10-07 13:39 ` Pavel Roskin [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=1128692383.13065.23.camel@dv \
--to=proski-mxxj517/zsq@public.gmane.org \
--cc=jkmaline-kf+aQKke1yb1KXRcyAk9cg@public.gmane.org \
--cc=meder-ljIgrh4ImVw@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=orinoco-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
/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;
as well as URLs for NNTP newsgroup(s).