View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006106 | Composr | securitylogging | public | 2025-01-02 20:04 | 2025-01-02 20:04 |
| Reporter | Patrick Schmalstig | Assigned To | Chris Graham | ||
| Severity | Minor-bug | ||||
| Status | assigned | Resolution | open | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0006106: Infinite loop if a block triggers a hack attack from POST data | ||||
| 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. | ||||
| Tags | Roadmap: v11 | ||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2025-01-02 20:04 | Patrick Schmalstig | New Issue | |
| 2025-01-02 20:04 | Patrick Schmalstig | Status | non-assigned => assigned |
| 2025-01-02 20:04 | Patrick Schmalstig | Assigned To | => Chris Graham |
| 2025-01-02 20:04 | Patrick Schmalstig | Tag Attached: Roadmap: v11 | |
| 2025-01-02 20:04 | Patrick Schmalstig | Description Updated | View Revisions |
