Pagure 5.2 API Key api_key_expire_mail.py information disclosure

Summaryinfo

A vulnerability has been found in Pagure 5.2 and classified as problematic. The impacted element is an unknown function of the file files/api_key_expire_mail.py of the component API Key Handler. Performing a manipulation results in information disclosure. This vulnerability is known as CVE-2019-7628. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Pagure 5.2. This affects an unknown part of the file files/api_key_expire_mail.py of the component API Key Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:

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

The bug was discovered 02/08/2019. The weakness was published 02/08/2019. This vulnerability is uniquely identified as CVE-2019-7628 since 02/07/2019. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

The commercial vulnerability scanner Qualys is able to test this issue with plugin 277629 (Fedora Security Update for pagure (FEDORA-2019-4e72b179e4)).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• Pagure

Version

• 5.2

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion