From: Florian Weimer <fw@deneb.enyo.de>
To: Andreas Gruenbacher <agruen@suse.de>
Cc: Trond Myklebust <Trond.Myklebust@netapp.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Olaf Kirch <okir@suse.de>
Subject: Re: Potential xdr_xcode_array2 security issue
Date: Thu, 23 Jun 2005 12:45:06 +0200 [thread overview]
Message-ID: <87hdfpz70t.fsf@deneb.enyo.de> (raw)
In-Reply-To: <200506231153.41318.agruen@suse.de> (Andreas Gruenbacher's message of "Thu, 23 Jun 2005 11:53:41 +0200")
* Andreas Gruenbacher:
> On Thursday 23 June 2005 07:48, Florian Weimer wrote:
>> This looks suspiciously like CVE-2002-0391.
>
> Thanks, Florian. How about the attached patch?
I don't know the code, so I can't tell if you must protect against
desc->elem_size beign zero. I also don't understand the second hunk.
next prev parent reply other threads:[~2005-06-23 10:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200506230502.j5N52PWP007955@hera.kernel.org>
2005-06-23 5:48 ` Potential xdr_xcode_array2 security issue (was: Re: [PATCH] RPC: Encode and decode arbitrary XDR arrays) Florian Weimer
2005-06-23 9:53 ` Andreas Gruenbacher
2005-06-23 10:45 ` Florian Weimer [this message]
2005-06-23 11:00 ` Potential xdr_xcode_array2 security issue Andreas Gruenbacher
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=87hdfpz70t.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=Trond.Myklebust@netapp.com \
--cc=agruen@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=okir@suse.de \
/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.