#6106 - Infinite loop if a block triggers a hack attack from POST data
| Identifier | #6106 |
|---|---|
| Issue type | Minor issue (breaks specific functionality) |
| Title | Infinite loop if a block triggers a hack attack from POST data |
| Status | Open |
| Tags |
Roadmap: v11 (custom) |
| Handling member | Chris Graham |
| Addon | securitylogging |
| Description | If a block triggers a hack attack (e.g. failed CAPTCHA), an infinite loop occurs because the hack attack generates the stack trace which then re-evaluates the block and thus re-actualises it and then triggers the hack attack again, and so on.
I added an infinite loop halt in hack attack, but this is just a bandage solution to a bigger problem. I cannot fix it. I tried un-setting POST parameters after hack attack logs and before it exits, but that did not work. |
| Steps to reproduce | |
| Funded? | No |
The system will post a comment when this issue is modified (e.g., status changes). To be notified of this, click "Enable comment notifications".

Comments
There have been no comments yet