CVE-2019-7628

MEDIUM

Pagure - Exposure of Sensitive Information via API Key Expiration Reminder E-Mail

Title source: llm
STIX 2.1

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

References (5)

Core 5
Core References
Issue Tracking, Patch, Vendor Advisory x_refsource_misc
https://pagure.io/pagure/c/9905fb1e64341822366b6ab1d414d2baa230af0a
Issue Tracking, Patch, Vendor Advisory x_refsource_misc
https://pagure.io/pagure/pull-request/4254
Issue Tracking, Patch, Vendor Advisory x_refsource_misc
https://pagure.io/pagure/issue/4230
Broken Link x_refsource_misc
https://pagure.io/pagure/issue/4252
Broken Link x_refsource_misc
https://pagure.io/pagure/issue/4253

Scores

CVSS v3 5.9
EPSS 0.0020
EPSS Percentile 41.8%
Attack Vector NETWORK
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Details

CWE
CWE-200
Status published
Products (1)
redhat/pagure 5.2
Published Feb 08, 2019
Tracked Since Feb 18, 2026