CERT® Advisory CA-1997-10 Vulnerability in Natural Language ServiceOriginal issue date: April 24, 1997
Last revised: September 26, 1997
Updated copyright statement
A complete revision history is at the end of this file.
The CERT Coordination Center has received reports of a buffer overflow condition that affects some libraries using the Natural Language Service (NLS) on UNIX systems. By exploiting this vulnerability, any local user can execute arbitrary programs as a privileged user. There is a possibility (with some old libraries) that the vulnerability can be exploited by a remote user.
Exploitation information is publicly available.
The CERT/CC team recommends installing patches when they become available.
We will update this advisory as we receive additional information. Please check advisory files regularly for updates that relate to your site.
A buffer overflow condition affects libraries using the Natural Language Service (NLS). The NLS is the component of UNIX systems that provides facilities for customizing the natural language formatting for the system. Examples of the types of characteristics that can be set are language, monetary symbols and delimiters, numeric delimiters, and time formats.
Some libraries that use a particular environment variable associated with the NLS contain a vulnerability in which a buffer overflow condition can be triggered. The particular environment variable involved is NLSPATH on some systems and PATH_LOCALE on others.
It is possible to exploit this vulnerability to attain unauthorized access by supplying carefully crafted arguments to programs that are owned by a privileged user-id and that have setuid or setgid bits set.
Exploit information involving this vulnerability has been made
Local users (users with access to an account on the system) are able to execute arbitrary programs as a privileged user without authorization. There is a possibility (with some old libraries) that the vulnerability can be exploited by a remote user.
Install a patch for this problem when one becomes available. Currently, there is no workaround to use in the meantime.
Below is a list of vendors who have provided information about this problem. Details are in Appendix A of this advisory; we will update the appendix as we receive more information. If your vendor's name is not on this list, the CERT/CC did not hear from that vendor. Please contact your vendor directly.
Berkeley Software Design, Inc. (BSDI)
Appendix A - Vendor InformationBelow is a list of the vendors who have provided information for this advisory. We will update this appendix as we receive additional information. If you do not see your vendor's name, the CERT/CC did not hear from that vendor. Please contact the vendor directly.
Berkeley Software Design, Inc. (BSDI)No versions of BSD/OS are vulnerable to this problem.
Cray Research - A Silicon Graphics CompanyThis problem has been resolved with code that is available in released software packages as described in the FIX AVAILABILITY section below.
FIX AVAILABILITYFor each affected product level, the following table identifies the release that contains the fix:
RELATED INFORMATIONSPR 704175 POSSIBLE SECURITY PROBLEM IN SETLOCALE
Data General CorporationWe're investigating.
Digital Equipment Corporation
SOURCE:Digital Equipment Corporation
Software Security Response Team
Copyright (c) Digital Equipment Corporation 1997. All rights reserved.
This reported problem is not present for Digital's ULTRIX or Digital
UNIX Operating Systems Software.
Hewlett-Packard CompanyHP has completed their testing, HP-UX is not vulnerable.
IBM CorporationAll AIX releases are vulnerable to a variation of this advisory.
AIX 3.2.5Apply the following fix to your system:
PTFs - U447656 U447671 U447676 U447682 U447705 U447723 (APAR IX67405)
To determine if you have these PTFs on your system, run the following command:
lslpp -lB U447656 U447671 U447676 U447682 U447705 U447723
AIX 4.1Apply the following fix to your system:
APAR - IX67407
To determine if you have this APAR on your system, run the following command:
instfix -ik IX67407
Or run the following command:
lslpp -h bos.rte.libc
Your version of bos.rte.libc should be 220.127.116.11 or later.
AIX 4.2Apply the following fixes to your system:
APAR - IX67377 IX65693
To determine if you have these APARs on your system, run the following command:
instfix -ik IX67377 IX65693
Or run the following command:
lslpp -h bos.rte.libc
Your version of bos.rte.libc should be 18.104.22.168 or later.
(APAR IX65693 fixes a problem with the mkgroup command after IX67377 is applied.)
To OrderAPARs may be ordered using Electronic Fix Distribution (via FixDist) or from the IBM Support Center. For more information on FixDist, reference URL:
or send e-mail to email@example.com
with a subject of "FixDist".
IBM and AIX are registered trademarks of International Business Machines
Linux SystemsLinux systems running older C libraries are vulnerable. To check which C library is being used type
linux% ldd /bin/ls
libc.so.5 => /lib/libc.so.5.3.12
This indicates the machine is using libc 5.3.12.
C libraries older than 5.3.12 (that is libc5.2.18, libc5.0.9 etc) are vulnerable to this bug and you should upgrade the C library. The release versions of libc 5.4.x are immune to this attack.
If you have libc5.3.12 it is insecure unless it is the modified libc5.3.12 shipped with Red Hat 4.1, or as an upgrade on Red Hat 4.0. You can check this with the package manager:
linux# rpm -q libc
Indicates you have version 17 of the package. This is the safe one.
Red Hat 4.0 users who have not already upgraded their libc can obtain this package at
NEC CorporationNEC platforms are not affected by this vulnerability.
NeXT/AppleNo versions of NeXTstep of OpenStep/Mach are vulnerable to this problem.
The Santa Cruz Operation (SCO)We are investigating this problem and will provide updated information for this advisory when it becomes available.
SolbourneSolbourne is not vulnerable.
Sun Microsystems, Inc.Not vulnerable.
The CERT Coordination Center staff thanks Wolfgang Ley of DFN-CERT for his input to this advisory and Bruce Ide for drawing our attention to the problem.
UPDATESThere appear to be several slightly different descriptions for the NLS acronym. They are included here for convenience:
National Language Service
This document is available from: http://www.cert.org/advisories/CA-1997-10.html
CERT/CC Contact Information
Phone: +1 412-268-7090 (24-hour hotline)
Fax: +1 412-268-6989
CERT/CC personnel answer the hotline 08:00-17:00 EST(GMT-5) / EDT(GMT-4) Monday through Friday; they are on call for emergencies during other hours, on U.S. holidays, and on weekends.
We strongly urge you to encrypt sensitive information sent by email. Our public PGP key is available from
If you prefer to use DES, please call the CERT hotline for more information.
Getting security information
CERT publications and other security information are available from our web site
* "CERT" and "CERT Coordination Center" are registered in the U.S. Patent and Trademark Office.
Conditions for use, disclaimers, and sponsorship information
Copyright 1997 Carnegie Mellon University.
Sep. 26, 1997 Updated copyright statement June 3, 1997 Updates section - added other phrases for the the NLS acronym Appendix A - updated Cray Research entry. May 1, 1997 Section III and Appendix. Updated vendor information for Hewlett-Packard Company. Acknowledgments - added a name upon receiving permission to do so.