An insertion of sensitive information into log file vulnerability was identified in the log files for a GitHub Enterprise Server back-end service that could permit an adversary in the middle attack when combined with other phishing techniques. To exploit this, an attacker would need access to the log files for the GitHub Enterprise Server appliance, a backup archive created with GitHub Enterprise Server Backup Utilities, or a service which received streamed logs. This vulnerability affected all versions of GitHub Enterprise Server since 3.7 and was fixed in version 3.7.19, 3.8.12, 3.9.7, 3.10.4, and 3.11.1.
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 |
|---|---|---|---|
| Enterprise_server | Github | 3.7.0 (including) | 3.17.19 (excluding) |
| Enterprise_server | Github | 3.8.0 (including) | 3.8.12 (excluding) |
| Enterprise_server | Github | 3.9.0 (including) | 3.9.7 (excluding) |
| Enterprise_server | Github | 3.10.0 (including) | 3.10.4 (excluding) |
| Enterprise_server | Github | 3.11.0 (including) | 3.11.0 (including) |
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: