In Redmine before 3.2.6 and 3.3.x before 3.3.3, remote attackers can obtain sensitive information (password reset tokens) by reading a Referer log, because account/lost_password does not use a redirect.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Redmine | Redmine | * | 3.2.5 (including) |
| Redmine | Redmine | 3.3.0 (including) | 3.3.0 (including) |
| Redmine | Redmine | 3.3.1 (including) | 3.3.1 (including) |
| Redmine | Redmine | 3.3.2 (including) | 3.3.2 (including) |
| Redmine | Ubuntu | artful | * |
| Redmine | Ubuntu | esm-apps/xenial | * |
| Redmine | Ubuntu | kinetic | * |
| Redmine | Ubuntu | trusty | * |
| Redmine | Ubuntu | upstream | * |
| Redmine | Ubuntu | xenial | * |
| Redmine | Ubuntu | zesty | * |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: