CVE-2019-7628
low-risk
Published 2019-02-08
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.)
Do I need to act?
-
0.20% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.9/10
Medium
NETWORK
/ HIGH complexity
Affected Products (1)
Pagure
Affected Vendors
References (10)
Issue Tracking
https://pagure.io/pagure/issue/4230
Broken Link
https://pagure.io/pagure/issue/4252
Broken Link
https://pagure.io/pagure/issue/4253
Issue Tracking
https://pagure.io/pagure/pull-request/4254
Issue Tracking
https://pagure.io/pagure/issue/4230
Broken Link
https://pagure.io/pagure/issue/4252
Broken Link
https://pagure.io/pagure/issue/4253
Issue Tracking
https://pagure.io/pagure/pull-request/4254
24
/ 100
low-risk
Severity
18/34 · Moderate
Exploitability
1/34 · Minimal
Exposure
5/34 · Minimal