Linux HAM/Amateur Radio development
 help / color / mirror / Atom feed
From: "IZ4EFN Alessio" <iz4efn@libero.it>
To: linux-hams@vger.kernel.org
Subject: Linuxnode vulnerability
Date: Sat, 28 Feb 2004 09:53:41 +0100	[thread overview]
Message-ID: <002201c3fdd8$5d944ff0$1400a8c0@IZ4EFN> (raw)
In-Reply-To: 1077935047.1249.3.camel@oh2bns.ampr.org

> As the author of LinuxNode I would be interested in what these bugs and
> exploits are... Please, anyone?
>
> --
> Tomi Manninen / OH2BNS / KP20ME04


Maybe I was too tired two nigth ago...looking for information about
Linuxnode on Google (just typed "Linuxnode").

Anyway I found these:

****

http://lists.alphanet.ch/pipermail/gull-annonces/2003-September/000075.html

LinuxNode Remote Buffer Overflow Vulnerability
BugTraq ID: 8512
Remote: Yes
Date Published: Aug 29 2003
Relevant URL: http://www.securityfocus.com/bid/8512
Summary:
LinuxNode is an amateur packet radio node program.
It has been reported that LinuxNode is prone to a remote buffer overflow
condition.  The issue presents itself due to insufficient bounds checking.
A remote attacker may ultimately exploit this issue remotely and execute
arbitrary code in the context of the user who is running the vulnerable
software.  Successful exploitation may allow a attacker to gain
unauthorized access to the vulnerable host.
Explicit technical details regarding this vulnerability are not currently
available. This BID will be updated, as further details regarding this
issue are made public.
Although LinuxNode 0.3.0 has been reported to be vulnerable to this
problem, other versions may be affected as well.

****

http://secunia.com/advisories/9632/

Here Morgan SM6TKY says to upgrade to 0.3.2:

Some vulnerabilities have been identified in LinuxNode, which can be
exploited by malicious people to compromise a vulnerable system.

The vulnerabilities are caused due to a boundary error in the
"expand_string()" function as well as some format string errors. These can
be exploted to execute arbitrary code on an affected system.

Solution:
Update to version 0.3.2:
http://hes.iki.fi/pub/ham/unix/linux/ax25/

****

This is quite interesting, it regards the possibility to gain access on the
running machine:

http://xforce.iss.net/xforce/xfdb/13077

LinuxNode is a freely available amateur packet radio node program for
Linux-based operating systems. LinuxNode versions 0.3.2 and earlier are
vulnerable to a format string attack. A remote attacker can exploit this
vulnerability to cause a denial of service or execute arbitrary code on the
system.

Platforms Affected:
Debian Project Debian Linux 3.0
Tomi Manninen LinuxNode 0.3.2 and earlier

Remedy:

For Debian GNU/Linux 3.0 (woody):
Upgrade to the latest node package (0.3.0a-2woody1 or later), as listed in
Debian Security Advisory DSA 375-1. See References.

Consequences:

Gain Access

****

http://securitylab.ru/40026.html

This is another SM6TKY advice, with a woody patch for Debian.

****

Don't know if this can be useful Tomi, if I these information are incorrect
or doesn't regard this system please exuse me.

Let me know,

Alessio Sacchi IZ4EFN.


  reply	other threads:[~2004-02-28  8:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-26 23:23 DX Spider and Kernel > 2.6.1 Ruben Navarro Huedo
2004-02-27 17:07 ` Jeroen Vreeken
2004-02-28  0:04   ` Would you run Linuxnode into an _OLD_ server? IZ4EFN Alessio
2004-02-28  2:24     ` Tomi Manninen
2004-02-28  8:53       ` IZ4EFN Alessio [this message]
2004-02-28 12:54         ` Linuxnode vulnerability Tomi Manninen
2004-03-01 21:16       ` Would you run Linuxnode Bob Morgan
2004-02-28  6:26     ` Would you run Linuxnode into an _OLD_ server? Aleksandar Ilic
2004-02-29  5:58     ` Rodolfo Brasnarof

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='002201c3fdd8$5d944ff0$1400a8c0@IZ4EFN' \
    --to=iz4efn@libero.it \
    --cc=linux-hams@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