CVE-2019-7628

N/A
Published: February 8, 2019 at 03:00 AM UTC
Updated: June 17, 2026 at 02:40 AM UTC
1 product affected across 1 vendorPagure

Using N/A by N/A?

Get instant alerts when new vulnerabilities affect N/A - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.9%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (5)

x_refsource_MISCIssue TrackingPatchVendor Advisory
https://pagure.io/pagure/c/9905fb1e64341822366b6ab1d414d2baa230af0a
x_refsource_MISCIssue TrackingPatchVendor Advisory
https://pagure.io/pagure/issue/4230
x_refsource_MISCIssue TrackingPatchVendor Advisory
https://pagure.io/pagure/pull-request/4254

CVSS

Confidentiality
PARTIAL
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-200

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card