Grav is a file-based Web platform. Prior to 1.8.0-beta.27, A Denial of Service (DoS) vulnerability has been identified in Grav related to the handling of scheduled_at parameters. Specifically, the application fails to properly sanitize input for cron expressions. By manipulating the scheduled_at parameter with a malicious input, such as a single quote, the application admin panel becomes non-functional, causing significant disruptions to administrative operations. The only way to recover from this issue is to manually access the host server and modify the backup.yaml file to correct the corrupted cron expression. This vulnerability is fixed in 1.8.0-beta.27.
The product does not properly control the allocation and maintenance of a limited resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Grav | Getgrav | * | 1.8.0 (excluding) |
| Grav | Getgrav | 1.8.0-beta1 (including) | 1.8.0-beta1 (including) |
| Grav | Getgrav | 1.8.0-beta10 (including) | 1.8.0-beta10 (including) |
| Grav | Getgrav | 1.8.0-beta11 (including) | 1.8.0-beta11 (including) |
| Grav | Getgrav | 1.8.0-beta12 (including) | 1.8.0-beta12 (including) |
| Grav | Getgrav | 1.8.0-beta13 (including) | 1.8.0-beta13 (including) |
| Grav | Getgrav | 1.8.0-beta14 (including) | 1.8.0-beta14 (including) |
| Grav | Getgrav | 1.8.0-beta15 (including) | 1.8.0-beta15 (including) |
| Grav | Getgrav | 1.8.0-beta16 (including) | 1.8.0-beta16 (including) |
| Grav | Getgrav | 1.8.0-beta17 (including) | 1.8.0-beta17 (including) |
| Grav | Getgrav | 1.8.0-beta18 (including) | 1.8.0-beta18 (including) |
| Grav | Getgrav | 1.8.0-beta19 (including) | 1.8.0-beta19 (including) |
| Grav | Getgrav | 1.8.0-beta2 (including) | 1.8.0-beta2 (including) |
| Grav | Getgrav | 1.8.0-beta20 (including) | 1.8.0-beta20 (including) |
| Grav | Getgrav | 1.8.0-beta21 (including) | 1.8.0-beta21 (including) |
| Grav | Getgrav | 1.8.0-beta22 (including) | 1.8.0-beta22 (including) |
| Grav | Getgrav | 1.8.0-beta23 (including) | 1.8.0-beta23 (including) |
| Grav | Getgrav | 1.8.0-beta24 (including) | 1.8.0-beta24 (including) |
| Grav | Getgrav | 1.8.0-beta25 (including) | 1.8.0-beta25 (including) |
| Grav | Getgrav | 1.8.0-beta26 (including) | 1.8.0-beta26 (including) |
| Grav | Getgrav | 1.8.0-beta3 (including) | 1.8.0-beta3 (including) |
| Grav | Getgrav | 1.8.0-beta4 (including) | 1.8.0-beta4 (including) |
| Grav | Getgrav | 1.8.0-beta5 (including) | 1.8.0-beta5 (including) |
| Grav | Getgrav | 1.8.0-beta6 (including) | 1.8.0-beta6 (including) |
| Grav | Getgrav | 1.8.0-beta7 (including) | 1.8.0-beta7 (including) |
| Grav | Getgrav | 1.8.0-beta8 (including) | 1.8.0-beta8 (including) |
| Grav | Getgrav | 1.8.0-beta9 (including) | 1.8.0-beta9 (including) |
Mitigation of resource exhaustion attacks requires that the target system either:
The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question.
The second solution is simply difficult to effectively institute – and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.