From: David Jacoby <dj@outpost24.com>
To: linux-kernel@vger.kernel.org
Subject: Linux kernel IGMP vulnerabilities
Date: Wed, 15 Dec 2004 09:43:29 +0100 [thread overview]
Message-ID: <41BFF931.6030205@outpost24.com> (raw)
Hi and Merry Xmas everyone!
I just have a little question, is there a way to turn on IGMP support in
the kernel?, I removed
multicast support but is that enugh?
They said that you could see if you are vulnerable by looking at these
files:
/proc/net/igmp
/proc/net/mcfilter
and if both existed and were non-emptu you were vulnerable.
On a defualt installation on Slackware 10 the files mcfilter
is empty but on other servers with various kernel versions
both files contains some data.
The slackware machine is running 2.4.24. As i said i removed
multicast support in the kernel but when i compiled it i saw
that it created igmp.o anyway.
Any advice about how people can patch this security issue?
Thnx!
//David
--
Outpost24 AB
David Jacoby
Research & Development
Office: +46-455-612310
Mobile: +46-455-612311
(www.outpost24.com) (dj@outpost24.com)
next reply other threads:[~2004-12-15 8:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-15 8:43 David Jacoby [this message]
2004-12-15 9:08 ` Linux kernel IGMP vulnerabilities YOSHIFUJI Hideaki / 吉藤英明
2004-12-15 11:49 ` Linux kernel IGMP vulnerabilities, PATCH IS BROKEN! David Jacoby
2004-12-15 11:54 ` Marc-Christian Petersen
2004-12-15 11:56 ` David Jacoby
[not found] ` <20041215120418.GA9049@tufnell.lon1.poggs.net>
2004-12-15 12:11 ` David Jacoby
2004-12-15 14:20 ` YOSHIFUJI Hideaki / 吉藤英明
2004-12-15 18:34 ` Chris Wright
2004-12-15 18:50 ` Phil Oester
2004-12-15 19:40 ` David S. Miller
2004-12-16 6:16 ` Willy Tarreau
2004-12-16 22:53 ` Bill Davidsen
2004-12-17 7:27 ` David Jacoby
2004-12-16 0:08 ` Linux kernel IGMP vulnerabilities Lukasz Trabinski
2004-12-16 10:24 ` Marcelo Tosatti
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=41BFF931.6030205@outpost24.com \
--to=dj@outpost24.com \
--cc=linux-kernel@vger.kernel.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