what you don't know can hurt you
Home Files News &[SERVICES_TAB]About Contact Add New

S-96-25.asc

S-96-25.asc
Posted Jan 10, 2000

Subject NIS+ configuration vulnerability Date 20-may-96

SHA-256 | 929c0e9442bbcb7b66ecb37e0b745da10751c5178d3b01bc8e180af7a3c1013b

S-96-25.asc

Change Mirror Download
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

===============================================================================
>> CERT-NL, 01-Mar-2000 <<
>> All CERT-NL information has been moved to http://cert.surfnet.nl. Links <<
>> to CERT-NL information contained in this advisory are therefore outdated. <<
>> <<
>> CERT-NL also has stopped the CERT-CC-Mirror service. Due to this the <<
>> links to the CERT-CC mirror are obsolete. Visit the CERT-CC site for the <<
>> complete CERT-CC advisory texts: http://www.cert.org <<
===============================================================================

===============================================================================
Security Advisory CERT-NL
===============================================================================
Author/Source : Gert Meijerink Index : S-96-25
Distribution : World Page : 1
Classification: External Version: 1
Subject : NIS+ configuration vulnerability Date : 20-may-96
===============================================================================

By courtesy of AUSCERT (the Australian CERT) we received information on a
vulnerability in the NIS+ configuration.

CERT-NL recommends that any site which has NIS+ installed take this opportunity
to check their installations and apply the appropriate workarounds as described
in Section 3.

==============================================================================

=============================================================================
AA-96.02 AUSCERT Advisory
NIS+ configuration vulnerability
20 May 1996
- - -----------------------------------------------------------------------------

AUSCERT has received information that a vulnerability exists under some
configurations of NIS+. In vulnerable installations of NIS+, the access rights
on the NIS+ passwd table are left in an unsecure state.

This vulnerability is known to exist in NIS+ installations initially created
on Solaris 2.5 servers. Similar vulnerabilities in NIS+ configurations may
also exist in previous versions of Solaris 2.

This vulnerability may allow any user with valid NIS+ credentials to gain
root privileges.

AUSCERT recommends that any site which has NIS+ installed take this
opportunity to check their installations and apply the appropriate workarounds
as described in Section 3.

- - -----------------------------------------------------------------------------

1. Description

NIS+ provides distributed network access to information sources such as
password, group and host information. It maintains this information in
the form of NIS+ tables. NIS+ tables contain the administrative
information normally supplied by local files (such as /etc/passwd). As
with the standard Unix administration files, setting secure permissions
on the NIS+ tables is of utmost importance in maintaining system security.

NIS+ provides a comprehensive set of access rights for NIS+ tables. This
includes permissions not only on NIS+ tables but also individual columns
and entries in those tables. Due to the added complexity, sites need to
be particularly diligent in ensuring that permissions on NIS+ tables (and
associated entries and columns) are secure.

AUSCERT encourages sites running NIS+ to gain a good understanding of
the permission model used by NIS+. A complete description may be found
in the NIS+ documentation set. The rest of this advisory assumes a good
understanding of NIS+ permission controls.

AUSCERT has received information that under some installations of NIS+
the permissions on the NIS+ passwd table are left in an unsecure state.

This vulnerability is known to exist in NIS+ installations initially
created on Solaris 2.5 servers. Similar vulnerabilities in NIS+
configurations may also exist in previous versions of Solaris 2.

2. Impact

Any user with login access to a client or server that uses NIS+ for
authentication may gain root privileges.

3. Workarounds

NIS+ uses an access control mechanism for granting access to NIS+ tables
which is similar (but not identical) to that used by the standard Unix
file system. NIS+ tables are assigned permissions for the NIS+ user
categories nobody, owner, group and world. NIS+ also has permissions
associated with columns and individual entries in NIS+ tables.

Under some installations of NIS+ the permissions of the NIS+ passwd
table and its columns are left in an unsecure state. These permissions
can be viewed using niscat(1).

To check the permissions on the NIS+ passwd table, sites can use:

# niscat -o passwd.org_dir

This should produce output similar to:

Object Name : passwd
Owner : myhost.mydomain.org.
Group : admin.mydomain.org.
Domain : org_dir.mydomain.org.
Access Rights : ----rmcdrmcd----
Time to Live : 12:0:0
Object Type : TABLE
Table Type : passwd_tbl
Number of Columns : 8
Character Separator : :
Search Path :
Columns :
[0] Name : name
Attributes : (SEARCHABLE, TEXTUAL DATA, CASE SENSITIVE)
Access Rights : r---------------
[1] Name : passwd
Attributes : (TEXTUAL DATA)
Access Rights : -----m----------
[2] Name : uid
Attributes : (SEARCHABLE, TEXTUAL DATA, CASE SENSITIVE)
Access Rights : r---------------
[3] Name : gid
Attributes : (TEXTUAL DATA)
Access Rights : r---------------
[4] Name : gcos
Attributes : (TEXTUAL DATA)
Access Rights : r---------------
[5] Name : home
Attributes : (TEXTUAL DATA)
Access Rights : r---------------
[6] Name : shell
Attributes : (TEXTUAL DATA)
Access Rights : r---------------
[7] Name : shadow
Attributes : (TEXTUAL DATA)
Access Rights : ----------------

This output shows two types of access rights associated with the NIS+
passwd table. First, the default access rights for the table, which are
given at the start of the output (----rmcdrmcd----). Second, the access
rights associated with each column.

In particular, sites should check the access rights on the columns of
the NIS+ passwd table. It should be noted that it appears that individual
entries of the passwd table are owned by individual users. The above
access rights do not allow a user to modify any part of their passwd
table entry besides their own passwd field. For many environments this is
acceptable. For sites who wish users to be able to change their shells
or gcos information those columns may have the (m)odify bit set for owner.
Other than this, the access rights on columns should appear as above.

Any additional access rights on the table or its columns besides those
shown above may allow a user to gain additional privileges, including
possibly root. Sites should completely understand the ramifications if
they allow additional access rights.

Sites may set the access rights on the NIS+ passwd table, as shown in the
above output, by issuing the following commands as root on the master NIS+
server.

To set the default access rights for the NIS+ passwd table:

# nischmod na-rmcd,og+rmcd passwd.org_dir

To set the column access rights on the NIS+ passwd table:

# nistbladm -u name=na-rmcd,n=r passwd.org_dir
# nistbladm -u passwd=na-rmcd,o=m passwd.org_dir
# nistbladm -u uid=na-rmcd,n=r passwd.org_dir
# nistbladm -u gid=na-rmcd,n=r passwd.org_dir
# nistbladm -u gcos=na-rmcd,n=r passwd.org_dir
# nistbladm -u home=na-rmcd,n=r passwd.org_dir
# nistbladm -u shell=na-rmcd,n=r passwd.org_dir
# nistbladm -u shadow=na-rmcd passwd.org_dir

After making any changes in access rights, AUSCERT recommends that sites
verify the changes they have made using niscat(1), as shown previously.

Sites that have replica NIS+ servers may use nisping(1m) to propagate
the changes to the replica servers in a timely manner.

4. Additional measures

AUSCERT recommends that sites take this opportunity to ensure that all
NIS+ tables have access rights in accordance with the local site security
policy. This also includes checking access rights on all the columns
and entries of the NIS+ tables in addition to the default access rights
of the tables themselves.

- - -----------------------------------------------------------------------------
AUSCERT wishes to thank Ivan Angus and David Clarke of ANU for reporting this
vulnerability and for their advice in the preparation of this advisory.
AUSCERT also acknowledges Marek Krawus of UQ, Reinhard Uebel and Mark
McPherson of QTAC for their assistance.
- - -----------------------------------------------------------------------------

The AUSCERT team have made every effort to ensure that the information
contained in this document is accurate. However, the decision to use the
information described is the responsibility of each user or organisation.
The appropriateness of this document for an organisation or individual system
should be considered before application in conjunction with local policies
and procedures. AUSCERT takes no responsibility for the consequences of
applying the contents of this document.


==============================================================================
CERT-NL is the Computer Emergency Response Team for SURFnet customers. SURFnet
is the Dutch network for educational, research and related institutes. CERT-NL
is a member of the Forum of Incident Response and Security Teams (FIRST).

All CERT-NL material is available under:
http://cert.surfnet.nl/

In case of computer or network security problems please contact your local
CERT/security-team or CERT-NL (if your institute is NOT a SURFnet customer
please address the appropriate (local) CERT/security-team).

CERT-NL is one/two hour(s) ahead of UTC (GMT) in winter/summer,
i.e. UTC+0100 in winter and UTC+0200 in summer (DST).

Email: cert-nl@surfnet.nl ATTENDED REGULARLY ALL DAYS
Phone: +31 302 305 305 BUSINESS HOURS ONLY
Fax: +31 302 305 329 BUSINESS HOURS ONLY
Snailmail: SURFnet bv
Attn. CERT-NL
P.O. Box 19035
NL - 3501 DA UTRECHT
The Netherlands

NOODGEVALLEN: 06 22 92 35 64 ALTIJD BEREIKBAAR
EMERGENCIES : +31 6 22 92 35 64 ATTENDED AT ALL TIMES
CERT-NL'S EMERGENCY PHONENUMBER IS ONLY TO BE USED IN CASE OF EMERGENCIES:
THE SURFNET HELPDESK OPERATING THE EMERGENCY NUMBER HAS A *FIXED*
PROCEDURE FOR DEALING WITH YOUR ALERT AND WILL IN REGULAR CASES RELAY IT
TO CERT-NL IN AN APPROPRIATE MANNER. CERT-NL WILL THEN CONTACT YOU.
===============================================================================

-----BEGIN PGP SIGNATURE-----
Version: PGP 6.5.1i

iQA/AwUBOL6IJzSYjBqwfc9jEQLAvQCggvan+3xBAupBLI4iF9iu0lAuZCQAn3+M
adFQf4HxPH7Ds/jylwkIlsgM
=6dUv
-----END PGP SIGNATURE-----
Login or Register to add favorites

File Archive:

April 2024

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Apr 1st
    10 Files
  • 2
    Apr 2nd
    26 Files
  • 3
    Apr 3rd
    40 Files
  • 4
    Apr 4th
    6 Files
  • 5
    Apr 5th
    26 Files
  • 6
    Apr 6th
    0 Files
  • 7
    Apr 7th
    0 Files
  • 8
    Apr 8th
    22 Files
  • 9
    Apr 9th
    14 Files
  • 10
    Apr 10th
    10 Files
  • 11
    Apr 11th
    13 Files
  • 12
    Apr 12th
    14 Files
  • 13
    Apr 13th
    0 Files
  • 14
    Apr 14th
    0 Files
  • 15
    Apr 15th
    30 Files
  • 16
    Apr 16th
    10 Files
  • 17
    Apr 17th
    22 Files
  • 18
    Apr 18th
    45 Files
  • 19
    Apr 19th
    8 Files
  • 20
    Apr 20th
    0 Files
  • 21
    Apr 21st
    0 Files
  • 22
    Apr 22nd
    11 Files
  • 23
    Apr 23rd
    68 Files
  • 24
    Apr 24th
    23 Files
  • 25
    Apr 25th
    0 Files
  • 26
    Apr 26th
    0 Files
  • 27
    Apr 27th
    0 Files
  • 28
    Apr 28th
    0 Files
  • 29
    Apr 29th
    0 Files
  • 30
    Apr 30th
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2022 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close