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

> Remote attackers can enumerate valid user email addresses due to missing rate limits, exposing user identities.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-999q-q58c-qc52

## What is CVE-2019-6120?

CVE-2019-6120 is a high-severity vulnerability in n/a, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in NiceHash Miner before 2.0.3.0. A missing rate limit while adding a wallet via Email address allows remote attackers to submit a large number of email addresses to identify valid ones. By exploiting this vulnerability with CVE-2019-6122 (Username Enumeration) an adversary can enumerate a large number of valid users' Email addresses.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

It affects 1 product.


Products: Nicehash Miner.

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

No fix has been published for CVE-2019-6120 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-6120 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-6121](https://insights.sbomify.com/CVE-2019-6121/): Missing authorization in n/a (low 3.7)
- [CVE-2019-6122](https://insights.sbomify.com/CVE-2019-6122/): Information disclosure in n/a (low 3.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6120 is a high-severity vulnerability in n/a, published on 6 Nov 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-6120 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-6120/ (Markdown: https://insights.sbomify.com/CVE-2019-6120/index.md)
```

## Sources

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

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