Description
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.)
Metrics
CVSS 3.0 5.9/10
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
References
- https://pagure.io/pagure/c/9905fb1e64341822366b6ab1d414d2baa230af0aIssue Tracking, Patch, Vendor Advisory
- https://pagure.io/pagure/issue/4230Issue Tracking, Patch, Vendor Advisory
- https://pagure.io/pagure/issue/4252Broken Link
- https://pagure.io/pagure/issue/4253Broken Link
- https://pagure.io/pagure/pull-request/4254Issue Tracking, Patch, Vendor Advisory
- https://pagure.io/pagure/c/9905fb1e64341822366b6ab1d414d2baa230af0aIssue Tracking, Patch, Vendor Advisory
- https://pagure.io/pagure/issue/4230Issue Tracking, Patch, Vendor Advisory
- https://pagure.io/pagure/issue/4252Broken Link
- https://pagure.io/pagure/issue/4253Broken Link
- https://pagure.io/pagure/pull-request/4254Issue Tracking, Patch, Vendor Advisory
Timeline
- Published
- Feb 8, 2019
- Last modified
- Jun 17, 2026
- NVD status
- Modified