CVE-2019-10884
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUniqkey 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceUniqkey Password Manager 1.14 has a domain/sub-domain confusion vulnerability in its credential autofill logic. The application uses incorrect domain matching that treats sub-domains as equivalent to their parent domains, causing credentials saved for example.com to be automatically offered for usersite.example.com, enabling phishing attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.14CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Uniqkey Password Manager is installedCheck for the presence of Uniqkey Password Manager application on the system using system inventory tools, browser extension managers, or installed programs listsAffected if Uniqkey Password Manager is not installed, the vulnerability does not apply
-
Confirm the installed version is 1.14Locate the application version information through the application's about dialog, add-ons manager, or system program details, then compare against the affected version = 1.14Affected if The installed version is not exactly 1.14, this specific CVE does not apply
-
Determine if credential autofill is enabledAccess the Uniqkey Password Manager settings and check whether the autofill or auto-login feature for web forms is turned onAffected if Autofill is disabled, the vulnerable domain matching logic is not triggered during normal use
-
Inspect the autofill domain matching behaviorCreate a test credential for a parent domain such as example.com, then attempt to log in on a subdomain like usersite.example.com and observe whether Uniqkey offers to fill credentials from the parent domainAffected if Credentials saved for the parent domain are offered for a subdomain, the vulnerable subdomain confusion behavior is present
A system is affected by this CVE only if Uniqkey Password Manager version 1.14 is installed, autofill is enabled, and the application incorrectly autofills credentials across domain boundaries to subdomains.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataThe vendor should implement proper domain boundary validation using Public Suffix List (PSL) or equivalent domain parsing to ensure credentials are only autofilled for exact domain matches or appropriately scoped sub-domains.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10884 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-10884 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data