#47939 Malformed cookie for LDAP Sync makes DS crash
Closed: wontfix None Opened 9 years ago by nhosoi.

Description of problem:
When Content Synchronization plugin enabled, passing malformed cookie to
ldapsearch makes DS crash.

How reproducible:
always

Steps to Reproduce:
1. make a fresh install of DS
2. enable Content Synchronization plugin and Retro Changelog plugin, restart
server
3. run ldapsearch with malformed cookie
ldapsearch -h localhost:389 -D "cn=Directory Manager" -w Secret123 -LLL -b
dc=example,dc=com -E sync=ro/"#"

Actual results:
Server crashes
ldapsearch -h localhost:389 -D "cn=Directory Manager" -w Secret123 -LLL -b
dc=example,dc=com -E sync=ro/"#"
ldap_result: Can't contact LDAP server (-1)

Expected results:
Server should not crash and report that cookie is invalid, like in this
example:
ldapsearch -h localhost:389 -D "cn=Directory Manager" -w Secret123 -LLL -b
dc=example,dc=com -E sync=ro/"##"
Content Sync Refresh Required (4096)
Additional information: Invalid session cookie


Reviewed by Ludwig (Thank you!!)

Pushed to master:
77989d3..8f540a6 master -> master
commit 8f540a6

Pushed to 389-ds-base-1.3.3:
29a4160..d87202a 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit d87202a

Metadata Update from @nhosoi:
- Issue assigned to nhosoi
- Issue set to the milestone: 1.3.3 - 10/31 (October)

7 years ago

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

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.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

3 years ago

Login to comment on this ticket.

Metadata