Executive Summary
| Informations | |||
|---|---|---|---|
| Name | CVE-2019-7628 | First vendor Publication | 2019-02-07 |
| Vendor | Cve | Last vendor Modification | 2019-02-21 |
Security-Database Scoring CVSS v3
| Cvss vector : CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N | |||
|---|---|---|---|
| Overall CVSS Score | 5.9 | ||
| Base Score | 5.9 | Environmental Score | 5.9 |
| impact SubScore | 3.6 | Temporal Score | 5.9 |
| Exploitabality Sub Score | 2.2 | ||
| Attack Vector | Network | Attack Complexity | High |
| Privileges Required | None | User Interaction | None |
| Scope | Unchanged | Confidentiality Impact | High |
| Integrity Impact | None | Availability Impact | None |
| Calculate full CVSS 3.0 Vectors scores | |||
Security-Database Scoring CVSS v2
| Cvss vector : (AV:N/AC:M/Au:N/C:P/I:N/A:N) | |||
|---|---|---|---|
| Cvss Base Score | 4.3 | Attack Range | Network |
| Cvss Impact Score | 2.9 | Attack Complexity | Medium |
| Cvss Expoit Score | 8.6 | Authentication | None Required |
| Calculate full CVSS 2.0 Vectors scores | |||
Detail
| 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.) |
Original Source
| Url : http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-7628 |
CWE : Common Weakness Enumeration
| % | Id | Name |
|---|---|---|
| 100 % | CWE-200 | Information Exposure |
CPE : Common Platform Enumeration
| Type | Description | Count |
|---|---|---|
| Application | 1 |
Sources (Detail)
Alert History
| Date | Informations |
|---|---|
| 2021-05-04 13:39:25 |
|
| 2021-04-22 02:49:53 |
|
| 2020-05-23 02:33:13 |
|
| 2019-02-22 12:07:51 |
|
| 2019-02-08 12:07:12 |
|
