Show filters
5 Total Results
Displaying 1-5 of 5
Sort by:
Attacker Value
Unknown
CVE-2019-11556
Disclosure Date: September 25, 2020 (last updated February 22, 2025)
Pagure before 5.6 allows XSS via the templates/blame.html blame view.
0
Attacker Value
Unknown
CVE-2016-1000037
Disclosure Date: November 06, 2019 (last updated November 08, 2023)
Pagure: XSS possible in file attachment endpoint
0
Attacker Value
Unknown
CVE-2019-7628
Disclosure Date: February 08, 2019 (last updated November 27, 2024)
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.)
0
Attacker Value
Unknown
CVE-2017-1002151
Disclosure Date: September 14, 2017 (last updated November 26, 2024)
Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper authorization
0
Attacker Value
Unknown
CVE-2016-1000007
Disclosure Date: October 07, 2016 (last updated November 25, 2024)
Pagure 2.2.1 XSS in raw file endpoint
0
