CVEvulnerability
CVE-2019-7628
5.9 MEDIUM
Official page ↗
- Status
- Modified
- Published
- 2019-02-08
- Last modified
- 2026-06-17
- Assigner
- [email protected]
- CVSS 3.0 ([email protected])
- 5.9 MEDIUM — CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- CVSS 2.0 ([email protected])
- 4.3 MEDIUM — AV:N/AC:M/Au:N/C:P/I:N/A:N
- Weaknesses
- CWE-200
Description
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.)
Affected configurations
• redhat pagure 5.2
Related
Weakness · CWE (1)
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor weakness
References
- https://pagure.io/pagure/c/9905fb1e64341822366b6ab1d414d2baa230af0a Issue Tracking, Patch, Vendor Advisory
- https://pagure.io/pagure/issue/4230 Issue Tracking, Patch, Vendor Advisory
- https://pagure.io/pagure/issue/4252 Broken Link
- https://pagure.io/pagure/issue/4253 Broken Link
- https://pagure.io/pagure/pull-request/4254 Issue Tracking, Patch, Vendor Advisory
- https://pagure.io/pagure/c/9905fb1e64341822366b6ab1d414d2baa230af0a Issue Tracking, Patch, Vendor Advisory
- https://pagure.io/pagure/issue/4230 Issue Tracking, Patch, Vendor Advisory
- https://pagure.io/pagure/issue/4252 Broken Link
- https://pagure.io/pagure/issue/4253 Broken Link
- https://pagure.io/pagure/pull-request/4254 Issue Tracking, Patch, Vendor Advisory