#989 sssd_be segfault when using both deref and paging control
Closed: Fixed None Opened 12 years ago by jhrozek.

This was reported off list by John Hodrien.

He found out that when paging is used while dereferencing an entry, sssd_be may segfault on the second page.

This was because paging returned the control to sdap_generic_search multiple times but sssd was freeing dereference control after the first search invocation. The subsequend sdap searched accessed memory that was already freed.


Fields changed

owner: somebody => jhrozek

Fields changed

status: new => assigned

Fields changed

patch: 0 => 1

Fields changed

component: SSSD => LDAP Provider
milestone: NEEDS_TRIAGE => SSSD 1.6.2

Fixed by:
- 64caba9 (master)
- b9fe041 (sssd-1-6)

resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => 0

Metadata Update from @jhrozek:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.6.2

7 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/2031

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