[8231] in bugtraq
Re: Breaking Finger in AIX 4.2
daemon@ATHENA.MIT.EDU (Troy A. Bollinger)
Tue Oct 20 19:58:28 1998
Mail-Followup-To: aaaaaaa <axon2017@STUDENTS.JOHNCO.CC.KS.US>,
BUGTRAQ@netspace.org
Date: Tue, 20 Oct 1998 18:38:06 -0500
Reply-To: "Troy A. Bollinger" <troy@AUSTIN.IBM.COM>
From: "Troy A. Bollinger" <troy@AUSTIN.IBM.COM>
X-To: aaaaaaa <axon2017@STUDENTS.JOHNCO.CC.KS.US>
To: BUGTRAQ@NETSPACE.ORG
In-Reply-To: <Pine.A32.3.91.981020092043.21102A-100000@students.johnco.cc.ks.us>; from
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa on
Tue, Oct 20, 1998 at 09:32:50AM -0500
Quoting aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa (axon2017@STUDENTS.JOHNCO.CC.KS.US):
> I just found this out yesterday, and I don't think it's been in the
> postings before, but on AIX (I tested this on 4.2) if one's gecos field
> is set to more than 99 characters, Finger starts acting really strange.
This is fixed with the following APARs:
Abstract: "HOT: CERT: possible buffer overflow in finger daemon"
4.1.x APAR: IX67317
4.2.x APAR: IX67318
4.3.x APAR: not vulnerable
IBM AIX APARs may be ordered using Electronic Fix Distribution (via the
FixDist program), or from the IBM Support Center. For more information
on FixDist, and to obtain fixes via the Internet, please reference
http://aix.software.ibm.com/support/rs6000
or send email to "aixserv@austin.ibm.com" with the word "FixDist" in the
"Subject:" line.
To facilitate ease of ordering all security related APARs for each AIX
release, security fixes are periodically bundled into a cumulative APAR.
For more information on these cumulative APARs including last update and
list of individual fixes, send email to "aixserv@austin.ibm.com" with
the word "subscribe Security_APARs" in the "Subject:" line.
>
> .-= axon2017@students.jccc.net =-.
--
Troy Bollinger troy@austin.ibm.com
AIX Security Development security-alert@austin.ibm.com
PGP keyid: 1024/0xB7783129 Troy's opinions are not IBM policy
