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.)
Advisories
Source ID Title
EUVD EUVD EUVD-2019-17161 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.)
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-04T20:54:27.895Z

Reserved: 2019-02-07T00:00:00

Link: CVE-2019-7628

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2019-02-08T03:29:00.327

Modified: 2024-11-21T04:48:25.373

Link: CVE-2019-7628

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses