Problem
If the /usr/bin/sar command is given an exceedingly long argument
to the o option, it will memory fault. This could allow a malicious
user to elevate their permissions. Solution
Please see the Security Advisory below for details.
______________________________________________________________________________SCO, Inc. Security AdvisorySubject: OpenServer 5.0.5 : sar -o buffer overflow
Advisory number: CSSA-2002-SCO.17
Issue date: 2002 May 01
______________________________________________________________________________1. Problem DescriptionIf the /usr/bin/sar command is given an exceedingly long argument to
the o option, it will memory fault. This could allow a malicious user
to elevate their permissions.2. Vulnerable Supported VersionsSystem Binary
----------------------------------------------------------------------
SCO OpenServer System Release 5.0.5 /usr/bin/sar
/usr/lib/sa/sadc
/usr/bin/cpusar
/usr/bin/mpsar3. SolutionThe proper solution is to install the latest packages.
4. OpenServer 5.0.54.1 Location of Fixed Binariesftp://stage.sco.com/pub/security/openserver/CSSA-2002-SCO.174.2 VerificationMD5 (VOL.000.000) = f912fe801263863956c257c4ef395570md5 is available for download from:ftp://stage.sco.com/pub/security/tools/4.3 Installing Fixed BinariesUpgrade the affected binaries with the following commands:
Download the VOL* files to the /tmp directory.
Run the custom command, specify an install from media images, and specify the /tmp directory as the location of the images.
5. ReferencesSpecific references for this advisory:noneSCO UNIX security resources:[link no longer available]SCO OpenLinux security resources:http://www.sco.com/support/security/index.htmlThis security fix closes SCO incidents sr862424, fz520480, erg712003.
6. DisclaimerSCO, Inc. is not responsible for the misuse of any of
the information we provide on this website and/or through our security
advisories. Our advisories are a service to our customers intended to
promote secure installation and use of SCO products.7. Acknowledgements SCO would like to thank KF <dotslash@snosoft.com> for discovering this
problem, researching it, alerting us, and for being patient, too.
______________________________________________________________________________