Description of problem: /usr/bin/ldclt -b "ou=people,dc=example,dc=com" -h 10.14.7.222 -p 3893 -w password -e esearch,randombinddn,randombinddnlow=10,randombinddnhigh=99,randomattrlist=cn:sn:uid:ou:telephoneNumber:facsimileTelephoneNumber:mobile:roomNumber -n 100 -I 32 -r 1 -R 9999 -f "uid=guestXX" -s subtree ldclt version 4.23 /usr/bin/ldclt: line 55: 30583 Segmentation fault (core dumped) ${dir}/${COMMAND} "$@" and #0 strlen () at ../sysdeps/x86_64/strlen.S:106 #1 0x00007fed5d98b480 in parseFilter (src=0x0, head=0x7fed5db9cba8 <mctx+488>, tail=0x7fed5db9cbb0 <mctx+496>, ndigits=0x7fed5db9cba0 <mctx+480>) at ldap/servers/slapd/tools/ldclt/ldclt.c:1225 #2 0x00007fed5d98bcc9 in basicInit () at ldap/servers/slapd/tools/ldclt/ldclt.c:1441 #3 0x00007fed5d982876 in main (argc=26, argv=0x7fff70d59d28) at ldap/servers/slapd/tools/ldclt/ldclt.c:3169 up (gdb) p *src Cannot access memory at address 0x0 1220 parseFilter ( 1221 char *src, 1222 char **head, 1223 char **tail, 1224 int *ndigits) 1225 { 1226 int i, j; 1227 1228 for (i=0 ; (i<strlen(src)) && (src[i]!='X') ; i++); 1229 *head = (char *)malloc(i+1); Version-Release number of selected component: 389-ds-base-1.3.3.5-1.fc21 Additional info: reporter: libreport-2.3.0 backtrace_rating: 4 cmdline: /usr/bin/ldclt-bin -h 10.14.7.222 -p 3893 -s subtree -b ou=people,dc=exmaple,dc=com -e randombinddn randombinddnlow=1000 randombinddnhigh=9999 -e random esearch -r 1 -R 9999 -e randomattrlist=cn:sn:uid:ou:telephoneNumber:facsimileTelephoneNumber:mobile:roomNumber:carLicense:displayName:givenName:initials:title:departmentNumber:employeeNumber:employeeType:preferredLanguage -n 2 -I 32 -q -f uid=guestXXXX crash_function: strlen executable: /usr/bin/ldclt-bin kernel: 3.17.6-300.fc21.x86_64 runlevel: N 3 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (3 frames) #0 strlen at ../sysdeps/x86_64/strlen.S:106 #1 parseFilter at ldap/servers/slapd/tools/ldclt/ldclt.c:1225 #2 basicInit at ldap/servers/slapd/tools/ldclt/ldclt.c:1441
Created attachment 976697 [details] File: backtrace
Created attachment 976698 [details] File: build_ids
Created attachment 976699 [details] File: cgroup
Created attachment 976700 [details] File: core_backtrace
Created attachment 976701 [details] File: dso_list
Created attachment 976702 [details] File: environ
Created attachment 976703 [details] File: exploitable
Created attachment 976704 [details] File: limits
Created attachment 976705 [details] File: maps
Created attachment 976706 [details] File: open_fds
Created attachment 976707 [details] File: proc_pid_status
Created attachment 976708 [details] File: var_log_messages
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '21'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 21 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.