Note:
This project will be discontinued after December 13, 2021. [more]
Product:
Pagure
(Redhat)Repositories |
Unknown: This might be proprietary software. |
#Vulnerabilities | 5 |
Date | Id | Summary | Products | Score | Patch | Annotated |
---|---|---|---|---|---|---|
2019-11-06 | CVE-2016-1000037 | Pagure: XSS possible in file attachment endpoint | Fedora, Enterprise_linux, Pagure | 6.1 | ||
2020-09-25 | CVE-2019-11556 | Pagure before 5.6 allows XSS via the templates/blame.html blame view. | Backports_sle, Leap, Pagure | 6.1 | ||
2016-10-07 | CVE-2016-1000007 | Pagure 2.2.1 XSS in raw file endpoint | Pagure | N/A | ||
2017-09-14 | CVE-2017-1002151 | Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper authorization | Pagure | N/A | ||
2019-02-08 | 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.) | Pagure | 5.9 |