Pagure
by Pagure
Source repositories
CVEs (6)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2024-47515 | Hig | 0.53 | 8.1 | 0.01 | Dec 24, 2024 | A vulnerability was found in Pagure. Support of symbolic links during repository archiving of repositories allows the disclosure of local files. This flaw allows a malicious user to take advantage of the Pagure instance. | ||
| CVE-2017-1002151 | Hig | 0.49 | 7.5 | 0.01 | Sep 14, 2017 | Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper authorization | ||
| CVE-2016-1000007 | Med | 0.40 | 6.1 | 0.01 | Oct 7, 2016 | Pagure 2.2.1 XSS in raw file endpoint | ||
| CVE-2019-11556 | 0.00 | — | 0.01 | Sep 25, 2020 | Pagure before 5.6 allows XSS via the templates/blame.html blame view. | |||
| CVE-2016-1000037 | 0.00 | — | 0.01 | Nov 6, 2019 | Pagure: XSS possible in file attachment endpoint | |||
| CVE-2019-7628 | 0.00 | — | 0.01 | Feb 8, 2019 | 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… |
- risk 0.53cvss 8.1epss 0.01
A vulnerability was found in Pagure. Support of symbolic links during repository archiving of repositories allows the disclosure of local files. This flaw allows a malicious user to take advantage of the Pagure instance.
- risk 0.49cvss 7.5epss 0.01
Pagure 3.3.0 and earlier is vulnerable to loss of confidentially due to improper authorization
- risk 0.40cvss 6.1epss 0.01
Pagure 2.2.1 XSS in raw file endpoint
- CVE-2019-11556Sep 25, 2020risk 0.00cvss —epss 0.01
Pagure before 5.6 allows XSS via the templates/blame.html blame view.
- CVE-2016-1000037Nov 6, 2019risk 0.00cvss —epss 0.01
Pagure: XSS possible in file attachment endpoint
- CVE-2019-7628Feb 8, 2019risk 0.00cvss —epss 0.01
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…