1151675 – NSLCD WRAPS LDAP USER UIDNUMBER > 2^31 SO UID IS WRONG (AND A NEGATIVE NUMBER)

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1151675 - NSLCD WRAPS LDAP USER UIDNUMBER > 2^31 SO UID IS WRONG (AND A NEGATIVE NUMBER)

Summary: NSLCD WRAPS LDAP USER UIDNUMBER > 2^31 SO UID IS WRONG (AND A NEGATIVE NUMBER)

Keywords:
Status:	CLOSED ERRATA
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	nss-pam-ldapd
Sub Component:
Version:	7.2
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	rc
Target Release:	---
Assignee:	Jakub Hrozek
QA Contact:	Martin Zelený
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2014-10-11 02:30 UTC by Luan Jianhai
Modified:	2018-04-10 17:25 UTC (History)
CC List:	4 users (show)
Fixed In Version:	nss-pam-ldapd-0.8.13-16.el7
Doc Type:	If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:	2018-04-10 17:24:59 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)
The patch to fix the issue. (4.34 KB, message/rfc822) 2014-10-11 02:34 UTC, Luan Jianhai	no flags	Details
View All

Links
System	ID	Private	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:0935	0	None	None	None	2018-04-10 17:25:33 UTC

Description Luan Jianhai 2014-10-11 02:30:31 UTC

Description of problem:
I found that  LDAP user accounts with a uidNumber greater than
2^31 experience PAM authentication failures. e.g. the following occurs when they try to authenticate:

[Mon Aug 18 09:56:35 2014] [error] [client aaa.bbb.ccc.ddd] PAM: user
'rohan_roy' - not authenticated: Authentication failure
[Mon Aug 18 10:49:04 2014] [error] [client aaa.bbb.ccc.ddd] PAM: user
'rohan_roy' - not authenticated: Authentication failure
[Mon Aug 18 11:52:57 2014] [error] [client aaa.bbb.ccc.ddd] PAM: user
'rohan_roy' - not authenticated: Authentication failure
[Mon Aug 18 11:53:09 2014] [error] [client aaa.bbb.ccc.ddd] PAM: user
'rohan_roy' - not authenticated: Authentication failure
[Mon Aug 18 11:53:50 2014] [error] [client aaa.bbb.ccc.ddd] PAM: user
'rohan_roy' - not authenticated: Authentication failure

# getent passwd rohan_roy
rohan_roy:x:2300000032:18010:Rohan
Roy:/Network/Servers/notapplicable.apple.com/vol/homedir3/rohan_roy:/bin/bash
ANALYSIS AND RESEARCH
---------------------
Local users with uidnumber > 2^31 work (works for customer, and I also tested
this). 

Version-Release number of selected component (if applicable):
  0.8.13-8

How reproducible:
  Create LDAP server, and authentic user by nss-pam-ldap will failure


Steps to Reproduce:
1. Create LDAP server, and Configure nss-pam-ldap to authentic user by ldap
2. Create user which uid larger than 2^31
3. Authentic will failure

Actual results:
  Failure to authentic the user which uid larger than 2^31

Expected results:
  Should to successful authentic the user which uid larger than 2^31

Additional info:
  uid_t/gid_t should be formatted as unsigned long

Comment 1 Luan Jianhai 2014-10-11 02:32:09 UTC

Upstream have fix the issue, and the issue commit is: 78627c "uid_t/gid_t should be formatted as unsigned long"

Comment 2 Luan Jianhai 2014-10-11 02:34:25 UTC

Created attachment 945894 [details]
The patch to fix the issue.

Comment 5 Jakub Hrozek 2016-02-09 04:54:25 UTC

We do not plan on updating nss-pam-ldapd in 7.3 after all.

Comment 15 errata-xmlrpc 2018-04-10 17:24:59 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:0935

Note You need to log in before you can comment on or make changes to this bug.