From: Daniel Ahlberg <aliz@gentoo.org>
To: gentoo-announce@gentoo.org
Subject: GLSA: nessus (200305-10)
Date: Tue, 27 May 2003 11:15:07 +0200 [thread overview]
Message-ID: <20030527091507.8E7C133742@mail1.tamperd.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- - - ---------------------------------------------------------------------
GENTOO LINUX SECURITY ANNOUNCEMENT 200305-10
- - - ---------------------------------------------------------------------
PACKAGE : nessus
SUMMARY : problems in scripting engine
DATE : 2003-05-27 09:15 UTC
EXPLOIT : remote
VERSIONS AFFECTED : <nessus-2.0.6a
FIXED VERSION : >=nessus-2.0.6a
CVE :
- - - ---------------------------------------------------------------------
- - From advisory:
"There exists some vulnerabilities in NASL scripting engine.
To exploit these flaws, an attacker would need to have a valid Nessus
account as well as the ability to upload arbitrary Nessus plugins in the
Nessus server (this option is disabled by default) or he/she would need to
trick a user somehow into running a specially crafted nasl script."
Read the full advisory at
http://marc.theaimsgroup.com/?l=bugtraq&m=105369506714849&w=2
SOLUTION
It is recommended that all Gentoo Linux users who are running
net-analyzer/nessus upgrade to nessus-2.0.6a as follows
emerge sync
emerge nessus
emerge clean
- - - ---------------------------------------------------------------------
aliz@gentoo.org - GnuPG key is available at http://cvs.gentoo.org/~aliz
- - - ---------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+0yyafT7nyhUpoZMRAhc5AJoDcuH24b4v2yK53aI5Ql8OvF0bjQCeKBgl
G7TUn5qJzfMnwrjMDqn5DH8=
=nrb6
-----END PGP SIGNATURE-----
reply other threads:[~2003-05-27 11:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030527091507.8E7C133742@mail1.tamperd.net \
--to=aliz@gentoo.org \
--cc=gentoo-announce@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