From: Daniel Ahlberg <aliz@gentoo.org>
To: gentoo-announce@gentoo.org
Subject: GLSA: man (200303-13)
Date: Tue, 18 Mar 2003 19:03:51 +0100 [thread overview]
Message-ID: <20030318180313.B0F7F5763@mail2.tamperd.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
- - ---------------------------------------------------------------------
GENTOO LINUX SECURITY ANNOUNCEMENT 200303-13
- - ---------------------------------------------------------------------
PACKAGE : man
SUMMARY : arbitrary code execution
DATE : 2003-03-18 18:03 UTC
EXPLOIT : local
VERSIONS AFFECTED : <1.5l
FIXED VERSION : >=1.5l
CVE : CAN-2003-0124
- - ---------------------------------------------------------------------
- From advisory:
"man 1.5l was released today, fixing a bug which results in arbitrary code
execution upon reading a specially formatted man file. The basic problem
is, upon finding a string with a quoting problem, the function my_xsprintf
in util.c will return "unsafe" (rather than returning a string which could
be interpreted by the shell). This return value is passed directly to
system(3) - meaning if there is any program named `unsafe`, it will execute
with the privs of the user."
Read the full advisory at:
http://marc.theaimsgroup.com/?l=bugtraq&m=104740927915154&w=2
SOLUTION
It is recommended that all Gentoo Linux users who are running
sys-apps/man upgrade to man-1.5l as follows:
emerge sync
emerge man
emerge clean
- - ---------------------------------------------------------------------
aliz@gentoo.org - GnuPG key is available at http://cvs.gentoo.org/~aliz
- - ---------------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+d1+AfT7nyhUpoZMRAoNEAKC6r3Fl0cMaewvVnLPR0GYy+6XqTQCfcil/
dq/EzzvG4HhvhsRan4s8oPY=
=EHNI
-----END PGP SIGNATURE-----
reply other threads:[~2003-03-19 16:07 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=20030318180313.B0F7F5763@mail2.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