Description of problem: python -c "print 'a'*2050"|a2p http://www.intelligentexploit.com/view-details.html?id=20492 Version-Release number of selected component: perl-5.16.3-266.fc19 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: a2p crash_function: yyparse executable: /usr/bin/a2p kernel: 3.14.23-100.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (1 frames) #0 yyparse at y.tab.c:2880
Created attachment 974146 [details] File: backtrace
Created attachment 974147 [details] File: cgroup
Created attachment 974148 [details] File: core_backtrace
Created attachment 974149 [details] File: dso_list
Created attachment 974150 [details] File: environ
Created attachment 974151 [details] File: exploitable
Created attachment 974152 [details] File: limits
Created attachment 974153 [details] File: maps
Created attachment 974154 [details] File: open_fds
Created attachment 974155 [details] File: proc_pid_status
Created attachment 974156 [details] File: var_log_messages
This happens even in Rawhide (perl-App-a2p-1.007-3.fc22.x86_64, perl-libs-5.20.1-315.fc22.x86_64). It starts to happen exactly since 2050 characters which are word characters.
I think this bug is caused by upstream having used a broken byacc to generate a2p.c. Grabbing the missing yacc-source file a2p.y from upstream's git (https://github.com/Leont/app-a2p/a2p.y) and regenerating a2p.c using Fedora 21's byacc (byacc-1.9.20130925-4.fc21) seems to fix this issue for me.
Created attachment 975930 [details] Proposed patch, implementing what I wrote in previous comment
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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.
perl-5.18.4-292.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/perl-5.18.4-292.fc20
Package perl-5.18.4-292.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing perl-5.18.4-292.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-2034/perl-5.18.4-292.fc20 then log in and leave karma (feedback).
perl-5.18.4-306.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/perl-5.18.4-306.fc21
perl-5.18.4-306.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
perl-5.18.4-292.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.