Pagure 5.2 leaks API keys by e-mailing them to users. Few e-mail servers validate TLS certificates, so it is easy for man-in-the-middle attackers to read these e-mails and gain access to Pagure on behalf of other users. This issue is found in the API token expiration reminder cron job in files/api_key_expire_mail.py; disabling that job is also a viable solution. (E-mailing a substring of the API key was an attempted, but rejected, solution.)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
| Link | Tags |
|---|---|
| https://pagure.io/pagure/c/9905fb1e64341822366b6ab1d414d2baa230af0a | patch vendor advisory issue tracking |
| https://pagure.io/pagure/pull-request/4254 | patch vendor advisory issue tracking |
| https://pagure.io/pagure/issue/4230 | patch vendor advisory issue tracking |
| https://pagure.io/pagure/issue/4252 | broken link |
| https://pagure.io/pagure/issue/4253 | broken link |