Medium severity · published Feb 8, 2019
CVE-2019-7628
Pagure 5.2 leaks API keys by e-mailing them to users
5.9
CVSS
0.9%
EPSS
No
On KEV
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.)
CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Confidentiality
High
Integrity
None
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.9% · higher than 60% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
PA
Pagure · Redhat
5.2 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2019-7628
CVE.org
https://www.cve.org/CVERecord?id=CVE-2019-7628
Issue Tracking
https://pagure.io/pagure/c/9905fb1e64341822366b6ab1d414d2baa230af0a
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
More from Pagure
7.5
CVE-2017-1002151
Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper authorization
7.1
CVE-2024-4981
Pagure: _update_file_in_git() follows symbolic links in temporary clones
6.5
CVE-2024-4982
Pagure: path traversal in view_issue_raw_file()
6.1
CVE-2019-11556
Pagure before 5.6 allows XSS via the templates/blame.html blame view
6.1
CVE-2016-1000037
Pagure: XSS possible in file attachment endpoint
