Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2009.0405 -- [FreeBSD]
libc: Access Privileged Data
27 April 2009
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: libc
Publisher: FreeBSD
Operating System: FreeBSD
Impact: Access Privileged Data
Access: Existing Account
Original Bulletin:
http://security.freebsd.org/advisories/FreeBSD-SA-09:07.libc.asc
- --------------------------BEGIN INCLUDED TEXT--------------------
- -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
=============================================================================
FreeBSD-SA-09:07.libc Security Advisory
The FreeBSD Project
Topic: Information leak in db(3)
Category: core
Module: libc
Announced: 2009-04-22
Credits: Jaakko Heinonen, Xin LI
Affects: All supported versions of FreeBSD.
Corrected: 2009-04-11 15:19:26 UTC (RELENG_7, 7.2-PRERELEASE)
2009-04-22 14:07:14 UTC (RELENG_7_1, 7.1-RELEASE-p5)
2009-04-22 14:07:14 UTC (RELENG_7_0, 7.0-RELEASE-p12)
2009-04-11 15:21:11 UTC (RELENG_6, 6.4-STABLE)
2009-04-22 14:07:14 UTC (RELENG_6_4, 6.4-RELEASE-p4)
2009-04-22 14:07:14 UTC (RELENG_6_3, 6.3-RELEASE-p10)
For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:http://security.FreeBSD.org/>.
I. Background
FreeBSD's C library (libc) contains code for creating and accessing
Berkeley DB 1.85 database files. Such databases are used extensively
in FreeBSD; for example, the system password files (/etc/passwd and
/etc/master.passwd) are normally accessed via their database files
(/etc/pwd.db and /etc/spwd.db).
II. Problem Description
Some data structures used by the database interface code are not properly
initialized when allocated.
III. Impact
Programs using the db(3) interface to create Berkeley database files may
"leak" sensitive information into database files. If those files can be
read by other users, this may result in the disclosure of sensitive
information such as login credentials.
IV. Workaround
No workaround is available, but systems without untrusted local users are
probably not affected (since remote attackers will in most cases not be
able to read such database files).
V. Solution
Perform one of the following:
1) Upgrade your vulnerable system to 6-STABLE, or 7-STABLE, or to the
RELENG_7_1, RELENG_7_0, RELENG_6_4, or RELENG_6_3 security branch
dated after the correction date.
2) To patch your present system:
The following patches have been verified to apply to FreeBSD 6.3, 6.4,
7.0, and 7.1 systems.
a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.
# fetch http://security.FreeBSD.org/patches/SA-09:07/libc.patch
# fetch http://security.FreeBSD.org/patches/SA-09:07/libc.patch.asc
b) Execute the following commands as root:
# cd /usr/src
# patch < /path/to/patch
# cd /usr/src/lib/libc
# make obj && make depend && make && make install
NOTE: On the amd64 platform, the above procedure will not update the
lib32 (i386 compatibility) libraries. On amd64 systems where the i386
compatibility libraries are used, the operating system should instead
be recompiled as described in
<URL:http://www.FreeBSD.org/handbook/makeworld.html>
NOTE: System administrators may wish to rebuild any system database files
which were created prior to applying this patch in case they contain
sensitive information.
VI. Correction details
The following list contains the revision numbers of each file that was
corrected in FreeBSD.
CVS:
Branch Revision
Path
- - -------------------------------------------------------------------------
RELENG_6
src/lib/libc/db/btree/bt_split.c 1.7.2.1
src/lib/libc/db/btree/bt_open.c 1.11.14.1
src/lib/libc/db/hash/hash_buf.c 1.7.14.1
src/lib/libc/db/mpool/mpool.c 1.12.2.1
src/lib/libc/db/README 1.1.40.1
RELENG_6_4
src/UPDATING 1.416.2.40.2.8
src/sys/conf/newvers.sh 1.69.2.18.2.10
src/lib/libc/db/btree/bt_split.c 1.7.12.2
src/lib/libc/db/hash/hash_buf.c 1.7.26.2
src/lib/libc/db/mpool/mpool.c 1.12.12.2
RELENG_6_3
src/UPDATING 1.416.2.37.2.15
src/sys/conf/newvers.sh 1.69.2.15.2.14
src/lib/libc/db/btree/bt_split.c 1.7.10.1
src/lib/libc/db/hash/hash_buf.c 1.7.24.1
src/lib/libc/db/mpool/mpool.c 1.12.10.1
RELENG_7
src/lib/libc/db/btree/bt_split.c 1.8.2.1
src/lib/libc/db/btree/bt_open.c 1.12.2.1
src/lib/libc/db/hash/hash_buf.c 1.8.2.1
src/lib/libc/db/mpool/mpool.c 1.13.2.1
src/lib/libc/db/README 1.1.50.1
RELENG_7_1
src/UPDATING 1.507.2.13.2.8
src/sys/conf/newvers.sh 1.72.2.9.2.9
src/lib/libc/db/btree/bt_split.c 1.8.6.2
src/lib/libc/db/hash/hash_buf.c 1.8.6.2
src/lib/libc/db/mpool/mpool.c 1.13.6.2
RELENG_7_0
src/UPDATING 1.507.2.3.2.16
src/sys/conf/newvers.sh 1.72.2.5.2.16
src/lib/libc/db/btree/bt_split.c 1.8.4.1
src/lib/libc/db/hash/hash_buf.c 1.8.4.1
src/lib/libc/db/mpool/mpool.c 1.13.4.1
- - -------------------------------------------------------------------------
Subversion:
Branch/path Revision
- - -------------------------------------------------------------------------
stable/6/ r190940
releng/6.4/ r191381
releng/6.3/ r191381
stable/7/ r190939
releng/7.1/ r191381
releng/7.0/ r191381
- - -------------------------------------------------------------------------
The latest revision of this advisory is available at
http://security.FreeBSD.org/advisories/FreeBSD-SA-09:07.libc.asc
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)
iEYEARECAAYFAknvJlkACgkQFdaIBMps37JcyACggmDk96JTy3G5gGlzMlNuVsV7
s5wAoIT2G2c3T6bYa7GeftWLpGGFo2Rp
=rdqD
- -----END PGP SIGNATURE-----
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
http://www.auscert.org.au/render.html?cid=1980
If you believe that your computer system has been compromised or attacked in
any way, we encourage you to let us know by completing the secure National IT
Incident Reporting Form at:
http://www.auscert.org.au/render.html?it=3192
===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072
Internet Email: auscert@auscert.org.au
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967
iD8DBQFJ9SigNVH5XJJInbgRAugwAJoDDKH/73uLe0MaVaoCg2nKLiLBfACZASAU
WD27tNEkpLI8fTuchDjm+G0=
=nO+R
-----END PGP SIGNATURE-----