Keep Track of the Latest Vulnerabilities
with SecurityTracker!
    Home    |    View Topics    |    Search    |    Contact Us    |   


Sign Up
Sign Up for Your FREE Weekly SecurityTracker E-mail Alert Summary
Instant Alerts
Buy our Premium Vulnerability Notification Service to receive customized, instant alerts
Put SecurityTracker Vulnerability Alerts on Your Web Site -- It's Free!
Become a Partner and License Our Database or Notification Service
Report a Bug
Report a vulnerability that you have found to SecurityTracker

Category:   Application (Generic)  >   Libuser Vendors:   Dahyabhai, Nalin
Libuser LDAP Account Creation Default Password May Let Users Bypass Security Controls
SecurityTracker Alert ID:  1024960
SecurityTracker URL:
CVE Reference:   CVE-2011-0002   (Links to External Site)
Date:  Jan 13 2011
Impact:   Modification of authentication information
Fix Available:  Yes  Vendor Confirmed:  Yes  
Version(s): prior to 0.57
Description:   A vulnerability was reported in Libuser. A remote or local user can bypass security controls.

The software may create LDAP users with default passwords. A remote or local user can login using a default password.

The specific impact depends on the application that uses libuser.

Impact:   A remote or local user can bypass password access controls in certain cases.
Solution:   The vendor has issued a fix (0.57).

The vendor's advisory is available at:

Vendor URL: (Links to External Site)
Cause:   Access control error, State error
Underlying OS:   Linux (Any), UNIX (Any)

Message History:   This archive entry has one or more follow-up message(s) listed below.
Jan 20 2011 (Red Hat Issues Fix) Libuser LDAP Account Creation Default Password May Let Users Bypass Security Controls   (
Red Hat has issued a fix for Red Hat Enterprise Linux 4, 5, and 6.

 Source Message Contents

Date:  Thu, 13 Jan 2011 22:11:25 +0000
Subject:  libuser


 	* Resolve an ambiguity about "password" value format that could cause setting
 	  a known plaintext password in LDAP accounts: the "files"/"shadow" and LDAP
 	  modules may not be used together any more, and the module interface ABI has
 	  changed to support this.
 	* Don't authenticate the user (in lchfn, lchsh, lpasswd) if the application
 	  is not set*id and it does not need elevated privileges.  In particular, this
 	  allows the above programs to be used for LDAP administration by unprivileged
 	* Change default crypt_style to sha512.
 	* Don't abort on invalid ID values.
 	* Miscellaneous bug fixes.


Go to the Top of This SecurityTracker Archive Page

Home   |    View Topics   |    Search   |    Contact Us

Copyright 2015, LLC