If slapi_search_internal_set_pb is called with a NULL 'base', the pblock does not contain operation/plugin_identity....
If the caller of slapi_search_internal_set_pb does not detect that before calling slapi_search_internal_callback_pb, then the thread is not 'allowed _operation' and call send_ldap_result_ext with pblock->pb_op being NULL => SIGSEV
All version
DS crash with a backtrack similar to the BZ
send_ldap_result_ext should check pb_op before dereferencing it
Metadata Update from @tbordaz: - Custom field origin adjusted to IPA - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1461437 - Custom field type adjusted to defect
<img alt="0001-Ticket-49291-slapi_search_internal_callback_pb-may-S.patch" src="/389-ds-base/issue/raw/7eae6cb7318f30a32fb9e89fcf199c90bed624eb6456900be365d09df669808c-0001-Ticket-49291-slapi_search_internal_callback_pb-may-S.patch" />
Metadata Update from @mreynolds: - Issue set to the milestone: 1.3.6.0
Metadata Update from @tbordaz: - Custom field reviewstatus adjusted to review
Metadata Update from @mreynolds: - Custom field reviewstatus adjusted to ack (was: review)
Counting objects: 6, done. Delta compression using up to 8 threads. Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 954 bytes | 0 bytes/s, done. Total 6 (delta 4), reused 0 (delta 0) To ssh://git@pagure.io/389-ds-base.git d42024e..ab81048 master -> master
Metadata Update from @tbordaz: - Custom field reviewstatus adjusted to review (was: ack)
Metadata Update from @tbordaz: - Issue assigned to tbordaz
Metadata Update from @tbordaz: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Thierry can you also commit this to the 1.3.6 branch please?
oppss sorry Mark
git push origin 389-ds-base-1.3.6 Counting objects: 6, done. Delta compression using up to 8 threads. Compressing objects: 100% (6/6), done. Writing objects: 100% (6/6), 957 bytes | 0 bytes/s, done. Total 6 (delta 4), reused 0 (delta 0) To ssh://git@pagure.io/389-ds-base.git 6bd1b7d..1a57b1d 389-ds-base-1.3.6 -> 389-ds-base-1.3.6
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/2350
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.