Kirby is a Content Management System. Prior to versions 3.5.8.2, 3.6.6.2, 3.7.5.1, and 3.8.1, a user enumeration vulnerability affects all Kirby sites with user accounts unless Kirbys API and Panel are disabled in the config. It can only be exploited for targeted attacks because the attack does not scale to brute force. The problem has been patched in Kirby 3.5.8.2, Kirby 3.6.6.2, Kirby 3.7.5.1, and Kirby 3.8.1. In all of the mentioned releases, the maintainers have rewritten the affected code so that the delay is also inserted after the brute force limit is reached.
The product generates an error message that includes sensitive information about its environment, users, or associated data.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Kirby | Getkirby | * | 3.5.8.2 (excluding) |
| Kirby | Getkirby | 3.6.0 (including) | 3.6.6.2 (excluding) |
| Kirby | Getkirby | 3.7.0 (including) | 3.7.5.1 (excluding) |
| Kirby | Getkirby | 3.8.0 (including) | 3.8.0 (including) |
| Kirby | Getkirby | 3.8.0-rc1 (including) | 3.8.0-rc1 (including) |
| Kirby | Getkirby | 3.8.0-rc2 (including) | 3.8.0-rc2 (including) |
| Kirby | Getkirby | 3.8.0-rc3 (including) | 3.8.0-rc3 (including) |
The sensitive information may be valuable information on its own (such as a password), or it may be useful for launching other, more serious attacks. The error message may be created in different ways:
An attacker may use the contents of error messages to help launch another, more focused attack. For example, an attempt to exploit a path traversal weakness (CWE-22) might yield the full pathname of the installed application. In turn, this could be used to select the proper number of “..” sequences to navigate to the targeted file. An attack using SQL injection (CWE-89) might not initially succeed, but an error message could reveal the malformed query, which would expose query logic and possibly even passwords or other sensitive information used within the query.