CVSS: 6.1EPSS: 0%CPEs: 3EXPL: 0CVE-2019-11556
https://notcve.org/view.php?id=CVE-2019-11556
Pagure before 5.6 allows XSS via the templates/blame.html blame view. Pagure versiones anteriores a 5.6, permite ataques de tipo XSS por medio de la vista dblame en el archivo templates/blame.html • http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00066.html http://lists.opensuse.org/opensuse-security-announce/2020-11/msg00007.html https://docs.pagure.org/pagure/changelog.html https://pagure.io/pagure/c/31a0d2950ed409550074ca52ba492f9b87ec3318?branch=ab39e95ed4dc8367e5e146e6d9a9fa6925b75618 https://pagure.io/pagure/commits/master • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •
CVSS: 5.9EPSS: 0%CPEs: 1EXPL: 0CVE-2019-7628
https://notcve.org/view.php?id=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.2 filtra las claves API enviándoselas a los usuarios por correo electrónico. • https://pagure.io/pagure/c/9905fb1e64341822366b6ab1d414d2baa230af0a https://pagure.io/pagure/issue/4230 https://pagure.io/pagure/issue/4252 https://pagure.io/pagure/issue/4253 https://pagure.io/pagure/pull-request/4254 • CWE-200: Exposure of Sensitive Information to an Unauthorized Actor •