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

> An attacker can enumerate valid user accounts by distinguishing error messages for invalid emails versus invalid credentials in NiceHash Miner.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rv55-37hq-r98j

## What is CVE-2019-6122?

CVE-2019-6122 is a low-severity vulnerability in n/a, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Username Enumeration via Error Message issue was discovered in NiceHash Miner before 2.0.3.0 because an "EMAIL DOES NOT EXIST" error message occurs whenever a submitted email address is incorrect, but there is a different error message for invalid credentials with a correct email address.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

It affects 1 product.


Products: Nicehash Miner.

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

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

## Is CVE-2019-6122 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6122 is a low-severity vulnerability in n/a, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-6122 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-6122/ (Markdown: https://insights.sbomify.com/CVE-2019-6122/index.md)
```

## Sources

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

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