CVE-2019-7628

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.)
References
Link Resource
https://pagure.io/pagure/c/9905fb1e64341822366b6ab1d414d2baa230af0a Issue Tracking Patch Vendor Advisory
https://pagure.io/pagure/issue/4230 Issue Tracking Patch Vendor Advisory
https://pagure.io/pagure/issue/4252 Broken Link
https://pagure.io/pagure/issue/4253 Broken Link
https://pagure.io/pagure/pull-request/4254 Issue Tracking Patch Vendor Advisory
Configurations

Configuration 1 (hide)

cpe:2.3:a:redhat:pagure:5.2:*:*:*:*:*:*:*

History

No history.

Information

Published : 2019-02-08 03:29

Updated : 2024-02-28 16:48


NVD link : CVE-2019-7628

Mitre link : CVE-2019-7628

CVE.ORG link : CVE-2019-7628


JSON object : View

Products Affected

redhat

  • pagure
CWE
CWE-200

Exposure of Sensitive Information to an Unauthorized Actor