Red Hat Pagure

Pagure: path traversal in view_issue_raw_file()

Pagure: _update_file_in_git() follows symbolic links in temporary clones

Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper authorization

Pagure: XSS possible in file attachment endpoint

Pagure before 5.6 allows XSS via the templates/blame.html blame view.

Pagure 2.2.1 XSS in raw file endpoint

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.)