#1922 sssd_be crashes when looking up users in the LDAP provider with ID mapping
Closed: Fixed None Opened 7 years ago by kaushikub.

sssd version: sssd-1.10.0-5.fc20.beta1

The domain section in sssd.conf has:

[domain/ADTEST]
debug_level = 0xFFF0
id_provider = ldap
ldap_uri = ldap://example.adtest.com
ldap_schema = ad
ldap_default_bind_dn = cn=Administrator,cn=Users,dc=adtest,dc=com
ldap_default_authtok = XXXXXX
ldap_tls_cacert = /etc/openldap/certs/ad_cert.pem
ldap_referrals = false

"getent passwd <username>" causes sssd_be to crash

The initial part of the backtrace shows:

Core was generated by `/usr/libexec/sssd/sssd_be --domain ADTEST --debug-to-files'.
Program terminated with signal 11, Segmentation fault.
#0  0xb679ae8c in sdap_attrs_get_sid_str (mem_ctx=mem_ctx@entry=0xb7d19828, idmap_ctx=0x0, sysdb_attrs=sysdb_attrs@entry=0xb7d1ae48, sid_attr=0xb68264e5 "objectSID", _sid_str=_sid_str@entry=0xbfda9f88) at src/providers/ldap/ldap_common.c:1586
1586        err = sss_idmap_bin_sid_to_sid(idmap_ctx->map,

Thread 1 (Thread 0xb6e31900 (LWP 32722)):
#0  0xb679ae8c in sdap_attrs_get_sid_str (mem_ctx=mem_ctx@entry=0xb7d19828, idmap_ctx=0x0, sysdb_attrs=sysdb_attrs@entry=0xb7d1ae48, sid_attr=0xb68264e5 "objectSID", _sid_str=_sid_str@entry=0xbfda9f88) at src/providers/ldap/ldap_common.c:1586
        ret = 0
        err = <optimized out>
        el = 0xb7d1af58
        sid_str = 0x1 <Address 0x1 out of bounds>

Fields changed

owner: somebody => jhrozek
status: new => assigned

Fields changed

patch: 0 => 1

milestone: NEEDS_TRIAGE => SSSD 1.10 beta
resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => 0

Metadata Update from @kaushikub:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.10 beta

3 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2964

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata