# CVE-2019-7628: Information disclosure in n/a

> Man-in-the-middle attackers can intercept API keys sent via email, allowing them to take over user accounts on Pagure.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Feb 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-6r84-2x5x-qp36, openSUSE-SU-2024:11139-1

## What is CVE-2019-7628?

CVE-2019-7628 is a medium-severity vulnerability in n/a, published on 8 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2019-7628?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pagure` | openSUSE:Tumbleweed | All versions | 5.13.2-2.2 |

Products: Redhat Pagure.

## How do I fix CVE-2019-7628?

Change a configuration setting.

## Is CVE-2019-7628 being exploited?

There is no known exploitation of CVE-2019-7628 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2024-4981](https://insights.sbomify.com/CVE-2024-4981/): Pagure: _update_file_in_git() follows symbolic links in temporary clones (high 7.6)
- [CVE-2024-4982](https://insights.sbomify.com/CVE-2024-4982/): Pagure: path traversal in view_issue_raw_file() (high 7.6)
- [CVE-2017-1002151](https://insights.sbomify.com/CVE-2017-1002151/): Missing authorization in Pagure (high 7.5)
- [CVE-2016-1000007](https://insights.sbomify.com/CVE-2016-1000007/): Pagure 2.2.1 XSS in raw file endpoint (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7628 and fix it if it is affected.

What it is: CVE-2019-7628 is a medium-severity vulnerability in n/a, published on 8 Feb 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-7628 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-7628/ (Markdown: https://insights.sbomify.com/CVE-2019-7628/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-7628
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-7628
- OSV: https://osv.dev/vulnerability/CVE-2019-7628

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-7628/
Summaries are generated and may contain mistakes; the official description above is the record.