CVE-2019-7628
Pagure API Key Exposure through Email
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.)
INFO
Published Date :
Feb. 8, 2019, 3:29 a.m.
Last Modified :
Feb. 21, 2019, 2:23 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
3.6
Exploitability Score :
2.2
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2019-7628.
| URL | Resource |
|---|---|
| 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 |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2019-7628 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2019-7628 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
Initial Analysis by [email protected]
Feb. 21, 2019
Action Type Old Value New Value Added CVSS V2 (AV:N/AC:M/Au:N/C:P/I:N/A:N) Added CVSS V3 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N Changed Reference Type https://pagure.io/pagure/c/9905fb1e64341822366b6ab1d414d2baa230af0a No Types Assigned https://pagure.io/pagure/c/9905fb1e64341822366b6ab1d414d2baa230af0a Issue Tracking, Patch, Vendor Advisory Changed Reference Type https://pagure.io/pagure/pull-request/4254 No Types Assigned https://pagure.io/pagure/pull-request/4254 Issue Tracking, Patch, Vendor Advisory Changed Reference Type https://pagure.io/pagure/issue/4230 No Types Assigned https://pagure.io/pagure/issue/4230 Issue Tracking, Patch, Vendor Advisory Changed Reference Type https://pagure.io/pagure/issue/4252 No Types Assigned https://pagure.io/pagure/issue/4252 Broken Link Changed Reference Type https://pagure.io/pagure/issue/4253 No Types Assigned https://pagure.io/pagure/issue/4253 Broken Link Added CWE CWE-200 Added CPE Configuration OR *cpe:2.3:a:redhat:pagure:5.2:*:*:*:*:*:*:*
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2019-7628 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2019-7628
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.14 }} 0.02%
score
0.50177
percentile