From: Rainer Groesslinger <scandium@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Security Problems: xmule, lmule
Date: Wed, 20 Aug 2003 01:08:30 +0200 [thread overview]
Message-ID: <200308200108.34719.scandium@gentoo.org> (raw)
In-Reply-To: <1061333257.14174.2.camel@localhost>
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1169 bytes --]
On Wednesday 20 August 2003 00:47, Patrick Lauer wrote:
> Hi,
>
> yesterday I found this:
> http://www.heise.de/newsticker/data/dab-18.08.03-000/ (in german)
>
> http://lists.netsys.com/pipermail/full-disclosure/2003-August/008449.
>html (english)
>
> short summary:
> all emule, lmule and xmule versions are vulnerable to buffer
> overflows including execution of malicious code.
>
> xmule 1.4.3 (portage current) is very vulnerable.
> xmule 1.5.6 (latest from xmule website) does not fix all known
> vulnerabilities.
>
> Please discourage the use of lmule and xmule until fixed versions are
> available.
lmule was removed from the tree several weeks ago because it isn't
developed anymore and unsupported for a few months now.
The problem - indeed - is, that even their latest unstable release
(1.5.6a) doesn't fix the problem and I observe xmule sharply and am
waiting for a fixed release or at least a patch.
I added an einfo about the security hole in all the xmule ebuilds and I
hope they release 1.4.4 or something soon (which will immediatly be
arch of course)
--
Rainer Groesslinger
http://dev.gentoo.org/~scandium/
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-08-19 23:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 22:47 [gentoo-dev] Security Problems: xmule, lmule Patrick Lauer
2003-08-19 23:08 ` Rainer Groesslinger [this message]
2003-08-19 23:19 ` Rainer Groesslinger
2003-08-19 23:25 ` Patrick Lauer
2003-08-19 23:32 ` Rainer Groesslinger
2003-08-19 23:51 ` Owen Gunden
2003-08-20 2:28 ` Georgi Georgiev
2003-08-27 13:43 ` Rainer Groesslinger
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=200308200108.34719.scandium@gentoo.org \
--to=scandium@gentoo.org \
--cc=gentoo-dev@gentoo.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