From: Patrick Lauer <gentoo@toso-digitals.de>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Security Problems: xmule, lmule
Date: 20 Aug 2003 00:47:37 +0200 [thread overview]
Message-ID: <1061333257.14174.2.camel@localhost> (raw)
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.
With best regards,
Patrick "bonsaikitten" Lauer
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-08-19 22:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-19 22:47 Patrick Lauer [this message]
2003-08-19 23:08 ` [gentoo-dev] Security Problems: xmule, lmule Rainer Groesslinger
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=1061333257.14174.2.camel@localhost \
--to=gentoo@toso-digitals.de \
--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