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 1135531 - sudo with ldap doesn't work with 'user id' in sudoUser option
Summary: sudo with ldap doesn't work with 'user id' in sudoUser option
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sudo
Version: 6.6
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Daniel Kopeček
QA Contact: Dalibor Pospíšil
URL:
Whiteboard:
Depends On:
Blocks: 1135539 1217621
TreeView+ depends on / blocked
 
Reported: 2014-08-29 14:30 UTC by David Spurek
Modified: 2016-05-10 21:42 UTC (History)
3 users (show)

Fixed In Version: sudo-1.8.6p3-21.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1135539 (view as bug list)
Environment:
Last Closed: 2016-05-10 21:42:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
proposed patch (1.25 KB, patch)
2015-12-14 09:16 UTC, Daniel Kopeček 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:0853 0 normal SHIPPED_LIVE sudo bug fix and enhancement update 2016-05-10 22:43:44 UTC

Description David Spurek 2014-08-29 14:30:03 UTC 
Description of problem:
sudo with ldap doesn't work with 'user id' in sudoUser option

set 'sudouser: ldap' in /etc/nsswitch.conf

[test]id userallowed
uid=10001(userallowed) gid=20001(groupallowed) groups=20001(groupallowed)

dn: cn=rule1,ou=Sudoers,dc=my-domain,dc=com
objectClass: top
objectClass: sudoRole
cn: rule1
sudoHost: ALL
sudoCommand: ALL
sudoUser: #10001

Version-Release number of selected component (if applicable):
sudo-1.8.6p3-15.el6

How reproducible:
always

Steps to Reproduce:
1.su - userallowed -c 'sudo true'
2.
3.

Actual results:
user isn't allowed to run sudo

Expected results:
user is allowed to run sudo


Additional info:
Comment 4 Daniel Kopeček 2015-02-24 15:26:16 UTC 
From the logs:
Aug 17 12:53:09 sudo[6575] <- sudo_ldap_lookup @ ./ldap.c:2480 := 64

In this case, the return value of 64 means:

FLAG_NO_HOST 0x040

and therefore no matching rules were found. Looks like a misconfiguration. Closing as not a bug. Reopen if you get the same results after ensuring that sudo is processing some rules and they don't match the user id...
Comment 5 David Spurek 2015-02-25 14:12:26 UTC 
I think that this is a real bug.

If I change sudoUser: #10001 to sudoUser: userallowed then everything works correctly:

[test]getent passwd useralloweduserallowed:x:10001:20001:userallowed:/home/userallowed:/bin/bash

dn: cn=rule1,ou=Sudoers,dc=my-domain,dc=com
objectClass: top
objectClass: sudoRole
cn: rule1
sudoHost: ALL
sudoCommand: ALL
sudoUser: userallowed

[test]su - userallowed -c 'sudo true'su: warning: cannot change directory to /home/userallowed: No such file or directory
[test]echo $?
0

--------------------------------------------
# Sudoers, my-domain.com
dn: ou=Sudoers,dc=my-domain,dc=com
objectClass: top
objectClass: organizationalUnit
ou: Sudoers

# defaults, Sudoers, my-domain.com
dn: cn=defaults,ou=Sudoers,dc=my-domain,dc=com
objectClass: top
objectClass: sudoRole
sudoOption: !authenticate
sudoOption: !requiretty
cn: defaults

# rule1, Sudoers, my-domain.com
dn: cn=rule1,ou=Sudoers,dc=my-domain,dc=com
objectClass: top
objectClass: sudoRole
cn: rule1
sudoHost: ALL
sudoCommand: ALL
sudoUser: #10001


[test]su - userallowed -c 'sudo true'
su: warning: cannot change directory to /home/userallowed: No such file or directory
userallowed is not allowed to run sudo on rhel6-6.  This incident will be reported.
[test]echo $?
1

------------------------------------
and with processing of other rules

[test]getent passwd userallowed2
userallowed2:usersecret:10003:20003:userallowed2:/home/userallowed2:/bin/bash

# Sudoers, my-domain.com
dn: ou=Sudoers,dc=my-domain,dc=com
objectClass: top
objectClass: organizationalUnit
ou: Sudoers

# defaults, Sudoers, my-domain.com
dn: cn=defaults,ou=Sudoers,dc=my-domain,dc=com
objectClass: top
objectClass: sudoRole
sudoOption: !authenticate
sudoOption: !requiretty
cn: defaults

# rule1, Sudoers, my-domain.com
dn: cn=rule1,ou=Sudoers,dc=my-domain,dc=com
objectClass: top
objectClass: sudoRole
cn: rule1
sudoHost: ALL
sudoCommand: ALL
sudoUser: #10001

# rule2, Sudoers, my-domain.com
dn: cn=rule2,ou=Sudoers,dc=my-domain,dc=com
objectClass: top
objectClass: sudoRole
cn: rule2
sudoHost: ALL
sudoCommand: ALL
sudoUser: userallowed2


[test]su - userallowed -c 'sudo true'su: warning: cannot change directory to /home/userallowed: No such file or directory
userallowed is not allowed to run sudo on rhel6-6.  This incident will be reported.
[test]echo $?
1
[test]su - userallowed2 -c 'sudo true'
su: warning: cannot change directory to /home/userallowed2: No such file or directory
[test]echo $?
0
Comment 9 Daniel Kopeček 2015-12-14 09:16:28 UTC 
Created attachment 1105522 [details]
proposed patch
Comment 13 errata-xmlrpc 2016-05-10 21:42:58 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://rhn.redhat.com/errata/RHBA-2016-0853.html
Note You need to log in before you can comment on or make changes to this bug.