Red Hat Pagure 5.2
Approved changes feed: RSS · Atom
cpe:2.3:a:redhat:pagure:5.2:*:*:*:*:*:*:*
part: a version: 5.2 update: *
| Vendor | Redhat (e942785a-ca89-506e-bd99-50782639cde3) |
|---|---|
| Product | Pagure (689ea340-5073-568d-9162-4a19b8eac8c7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:deb/debian/pagure |
purl2cpe | 2026-06-01 10:12:53.638072 |
pkg:deb/ubuntu/pagure |
purl2cpe | 2026-06-01 10:12:53.638073 |
pkg:github/pagure/pagure |
purl2cpe | 2026-06-01 10:12:53.638074 |
pkg:rpm/fedora/pagure |
purl2cpe | 2026-06-01 10:12:53.638076 |
pkg:rpm/opensuse/pagure |
purl2cpe | 2026-06-01 10:12:53.638077 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-7628 |
vulnerable | 2026-06-08 05:14:14.594017 |
Details available
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.)
Published: 2019-02-08T03:00:00.000Z
Updated: 2024-08-04T20:54:27.895Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.