# CVE-2019-10884: Security feature bypass in n/a

> Uniqkey Password Manager incorrectly matches passwords across subdomains, potentially aiding phishing attacks by suggesting credentials for unrelated sites.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 5 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-25x6-6mr7-9jx8

## What is CVE-2019-10884?

CVE-2019-10884 is a high-severity vulnerability in n/a, published on 5 Apr 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

Uniqkey Password Manager 1.14 contains a vulnerability because it fails to recognize the difference between domains and sub-domains. The vulnerability means that passwords saved for example.com will be recommended for usersite.example.com. This could lead to successful phishing campaigns and create a sense of false security.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Uniqkey Password Manager.

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

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

## Is CVE-2019-10884 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-10676](https://insights.sbomify.com/CVE-2019-10676/): Information disclosure in n/a (medium 6.5)
- [CVE-2019-10845](https://insights.sbomify.com/CVE-2019-10845/): Security feature bypass in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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