An Information Exposure issue in the Terraform deployment step in Octopus Deploy before 2019.1.8 (and before 2018.10.4 LTS) allows remote authenticated users to view sensitive Terraform output variables via log files.
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 |
|---|---|---|---|
| Octopus_deploy | Octopus | * | 2018.9.17 (including) |
| Octopus_deploy | Octopus | 2018.10.0 (including) | 2018.10.0 (including) |
| Octopus_deploy | Octopus | 2018.10.1 (including) | 2018.10.1 (including) |
| Octopus_deploy | Octopus | 2018.10.2 (including) | 2018.10.2 (including) |
| Octopus_deploy | Octopus | 2018.10.3 (including) | 2018.10.3 (including) |
| Octopus_server | Octopus | 2018.11.0 (including) | 2019.1.8 (excluding) |
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: