Description of problem: I have probably run bashcheck script which tests for ShellShock vulnerability. Version-Release number of selected component: bash-4.3.25-2.fc21 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/bash -c 'f(){ x(){ _;};x(){ _;}<<a;}' crash_function: strlen executable: /usr/bin/bash kernel: 3.16.3-302.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1002 Truncated backtrace: Thread no. 1 (10 frames) #0 strlen at ../sysdeps/x86_64/strlen.S:106 #1 copy_redirect at copy_cmd.c:129 #2 copy_redirects at copy_cmd.c:164 #3 copy_command at copy_cmd.c:371 #4 copy_function_def_contents at copy_cmd.c:335 #5 bind_function_def at variables.c:2890 #6 make_function_def at make_cmd.c:801 #7 yyparse at ./parse.y:905 #8 parse_command at eval.c:239 #9 parse_and_execute at evalstring.c:299 Potential duplicate: bug 1148661
Created attachment 945833 [details] File: backtrace
Created attachment 945834 [details] File: cgroup
Created attachment 945835 [details] File: core_backtrace
Created attachment 945836 [details] File: dso_list
Created attachment 945837 [details] File: environ
Created attachment 945838 [details] File: exploitable
Created attachment 945839 [details] File: limits
Created attachment 945840 [details] File: maps
Created attachment 945841 [details] File: open_fds
Created attachment 945842 [details] File: proc_pid_status
Created attachment 945843 [details] File: var_log_messages
Hey Łukasz, this should now be fixed, please reopen this bug if you still experience this issue.