Solaris/SEAM Kerberos 5 Vulnerability Due To Buffer Overflows In krb5_aname_to_localname()


StatusIssued

DescriptionTop
Sun(sm) Alert Notification
  • Sun Alert ID: 101512 (formerly 57580)
  • Synopsis: Solaris/SEAM Kerberos 5 Vulnerability Due To Buffer Overflows In krb5_aname_to_localname()
  • Category: Security
  • Product: Solaris 9 Operating System, Solaris 7 Operating System, Solaris 8 Operating System
  • BugIDs: 5055875
  • Avoidance: Patch
  • State: Resolved
  • Date Released: 10-Jun-2004, 30-Sep-2004
  • Date Closed: 30-Sep-2004
  • Date Modified: 30-Sep-2004, 28-Sep-2004, 24-Sep-2004, 22-Sep-2004

1. Impact

On Kerberos 5 enabled systems using "auth_to_local" mapping through appropriate entries in the krb5 configuration file krb5.conf(4), an unprivileged local or remote user with kerberos credentials may be able to execute arbitrary code with root privileges due to buffer overflows in "krb5_aname_to_localname()" function.

This issue is described in CERT vulnerability VU#686862 at http://www.kb.cert.org/vuls/id/686862 and MIT krb5 Security Advisory 2004-001 at http://web.mit.edu/kerberos/advisories/MITKRB5-SA-2004-001-an_to_ln.txt.

2. Contributing Factors

This issue can occur in the following releases:

SPARC Platform

x86 Platform

Notes:

  1. Systems running Solaris Enterprise Authentication Mechanism (SEAM) 1.0.1 for Solaris 8 and SEAM 1.0.2 for Solaris 9 are impacted by this issue as SEAM 1.0.1 and 1.0.2 use the affected Kerberos libraries delivered in Solaris.
  2. Solaris Enterprise Authentication Mechanism (SEAM) is an unbundled product available for Solaris 7, 8 and 9. For more information on SEAM, please see the SEAM(5) man page.

For Solaris without SEAM, this issue may only occur if the system is configured to be a Kerberos client, verified by running the following command:

    % grep default_realm /etc/krb5/krb5.conf | grep -v __default_realm__
    default_realm = EXAMPLE.COM

If the command returns no output or the krb5.conf(4) file is not found, then the system is not configured for Kerberos.

In addition, systems are only vulnerable to this issue if they have been configured to enable the "explicit" mapping or "rules-based" mapping of the principal mapping functionality. This is not the default configuration. A system which is vulnerable will have one of the following entries in the krb5 configuration file (see krb5.conf(4)):

The explicit mapping form is similar to:

    auth_to_local_names = {
            aname = lname
    }

The rule-based mapping form is similar to:

    auth_to_local = RULE:foo

3. Symptoms

There are no predictable symptoms that would indicate the described issue has been exploited.


Solution SummaryTop

4. Relief/Workaround

To work around the described issue, disable the "auth_to_local" rules by commenting out the code for "auth_to_local" from the "/etc/krb5/krb5.conf" configuration file.


5. Resolution

This issue is addressed in the following releases:

SPARC Platform

x86 Platform

Note: For Solaris 8, both patches must be installed to resolve this issue.

Note: Although this issue is shown to be resolved in patch release 112908-15 (see patch README), that patch revision has been obsoleted is no longer available for download. Please use 112908-16 or later.


Change History

30-Sep-2004:
  • Final patches released for Resolution; re-release as Resolved
28-Sep-2004:
  • Patch 112908-15 is no longer available
24-Sep-2004:
  • Patch 112908-15 placed temporarily on Hold
22-Sep-2004:
  • Patches and T-Patches added to "Contributing Factors," "Relief/Workaround," and "Resolution" sections

This Sun Alert notification is being provided to you on an "AS IS" basis. This Sun Alert notification may contain information provided by third parties. The issues described in this Sun Alert notification may or may not impact your system(s). Sun makes no representations, warranties, or guarantees as to the information contained herein. ANY AND ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY DISCLAIMED. BY ACCESSING THIS DOCUMENT YOU ACKNOWLEDGE THAT SUN SHALL IN NO EVENT BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, PUNITIVE, OR CONSEQUENTIAL DAMAGES THAT ARISE OUT OF YOUR USE OR FAILURE TO USE THE INFORMATION CONTAINED HEREIN. This Sun Alert notification contains Sun proprietary and confidential information. It is being provided to you pursuant to the provisions of your agreement to purchase services from Sun, or, if you do not have such an agreement, the Sun.com Terms of Use. This Sun Alert notification may only be used for the purposes contemplated by these agreements.

Copyright 2000-2006 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, CA 95054 U.S.A. All rights reserved.


 
 
Login Required

You must login and have a valid contract to access Sun's Premium content which includes:

  • Sun Alerts
  • Bugs
  • Patches
  • Solutions
  • White Papers
  • Documentation
  • Support Knowledge

Login Required

You must login and have a valid contract to access Sun's contracted features

Access Legend:

(Login to access)   Sun Contracted Content
(Login to access)   Sun Contracted Feature

Please make use of SunSolve Feedback application by selecting the floating [+] to provide feedback about this specific document.

Search

Article Details
Article ID : 101512
Article Type : Sun Alert Notifications
Last reviewed : 2006-02-02
Audience : PUBLIC
Keywords :
Provide feedback  (help)
Page Tools
»  Print This Page
»  Email This Article
»  Bookmark This Article