Users login

Create an account »


Users login

Home » Hacking News » Trustix TSLSA-2003-0014: glibc integer overflow

Trustix TSLSA-2003-0014: glibc integer overflow

by Nikola Strahija on March 28th, 2003 An integer overflow was found in glibc 2.3.1 and earlier. The problem lies in the xdrmem_getbytes() function, which could possibly allow execution of arbitrary code.

Hash: SHA1

- --------------------------------------------------------------------------
Trustix Secure Linux Security Advisory #2003-0014

Package name: glibc
Summary: xdr / rpc
Date: 2003-03-26
Affected versions: TSL 1.1, 1.2, 1.5

- --------------------------------------------------------------------------
Package description:
The glibc package contains standard libraries which are used by multiple
programs on the system. In order to save disk space and memory, as well as to
make upgrading easier, common system code is kept in one place and shared
between programs. This particular package contains the most important sets of
shared libraries: the standard C library and the standard math library.
Without these two libraries, a Linux system will not function. The glibc
package also contains national language (locale) support and timezone

Problem description:
An integer overflow was discovered in the xdrmem_getbytes() function of
glibc 2.3.1 and earlier. This function is part of the XDR encoder/decoder
derived from Sun's RPC implementation.

This vulnerability might cause buffer overflows and could possibly be
exploited to execute arbitray code.

We recommend that all systems with this package installed be upgraded.

All TSL updates are available from

About Trustix Secure Linux:
Trustix Secure Linux is a small Linux distribution for servers. With focus
on security and stability, the system is painlessly kept safe and up to
date from day one using swup, the automated software updater.

Automatic updates:
Users of the SWUP tool can enjoy having updates automatically
installed using 'swup --upgrade'.

Get SWUP from:

Public testing:
These packages have been available for public testing for some time.
If you want to contribute by testing the various packages in the
testing tree, please feel free to share your findings on the
tsl-discuss mailinglist.
The testing tree is located at

Check out our mailing lists:

This advisory along with all TSL packages are signed with the TSL sign key.
This key is available from:

The advisory itself is available from the errata pages at and
or directly at

MD5sums of the packages:
- --------------------------------------------------------------------------
fe9c277153f6d22fdafd8a214401563f ./1.5/SRPMS/glibc-2.1.3-22tr.src.rpm
a10d5a882dc223fbbac01f0693537da4 ./1.5/RPMS/nscd-2.1.3-22tr.i586.rpm
e5a446cd2fb6989d15614d71c7d0177c ./1.5/RPMS/glibc-profile-2.1.3-22tr.i586.rpm
e40a865a6369976eb600853548c34527 ./1.5/RPMS/glibc-devel-2.1.3-22tr.i586.rpm
14dab8234b4c08ff4cbd31fde948d1f1 ./1.5/RPMS/glibc-2.1.3-22tr.i586.rpm
fe9c277153f6d22fdafd8a214401563f ./1.2/SRPMS/glibc-2.1.3-22tr.src.rpm
4c4cab0eba6f73076e507efe1e2f06dc ./1.2/RPMS/nscd-2.1.3-22tr.i586.rpm
3262c2d809b651441af57ec792dfed11 ./1.2/RPMS/glibc-profile-2.1.3-22tr.i586.rpm
6c48f30edec63f62a8cf1d763c734c1c ./1.2/RPMS/glibc-devel-2.1.3-22tr.i586.rpm
97f7bd6d43c497b5978a8d86928027b3 ./1.2/RPMS/glibc-2.1.3-22tr.i586.rpm
fe9c277153f6d22fdafd8a214401563f ./1.1/SRPMS/glibc-2.1.3-22tr.src.rpm
885a9828bf112e1b123bb24deda2191c ./1.1/RPMS/nscd-2.1.3-22tr.i586.rpm
da31eac54e4c326df5e28035d754df23 ./1.1/RPMS/glibc-profile-2.1.3-22tr.i586.rpm
c177de4109b197c58021f8b32808f611 ./1.1/RPMS/glibc-devel-2.1.3-22tr.i586.rpm
155859e8c46919b1f9679a9746776b9a ./1.1/RPMS/glibc-2.1.3-22tr.i586.rpm
- --------------------------------------------------------------------------

Trustix Security Team

Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see


Newsletter signup

Signup to our monthly newsletter and stay in touch with IT news!

Free E-books

We've got ebooks! But they're not online. :( Please give us a few days to bring downloads back.


Have something to say or just wanna drop us a line? Please keep this in mind: to spam, we reply with spam.

Contact us »