dbcve.org
JqueyApplication · Jquey Project

CVE-2017-16204

HIGH · 7.5 CVSS v3.0 Published 2018-06-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The jquey module exfiltrates sensitive data such as a user's private SSH key and bash history to a third party server during installation.

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 confidence

The 'jquey' npm package (a typosquat of jquery) contains malicious code that during installation exfiltrates sensitive user files including private SSH keys (~/.ssh/id_rsa, id_dsa, id_ecdsa, id_ed25519) and bash history (~/.bash_history) to an unknown remote third-party server.

MitigationImmediately remove the jquey package if present in any environment, rotate all SSH keys that may have been present on affected systems, and audit for unauthorized network connections to unknown servers.

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
JqueyApplication
Affected:= 1.0.1

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if jquey package is installed
    Run 'npm list jquey' or 'yarn list jquey' to see if the package is present in node_modules
    Affected if The jquey package appears in the package list at version 1.0.1
  2. Inspect package.json dependencies
    Search package.json files in your project for 'jquey' in the dependencies, devDependencies, or peerDependencies sections
    Affected if jquey is listed as a dependency at version 1.0.1
  3. Verify package installation location
    Check for the presence of node_modules/jquey directory and examine its package.json file
    Affected if A node_modules/jquey directory exists with package.json showing version 1.0.1
  4. Audit installed npm packages for typosquat variants
    List all installed packages using 'npm list --depth=0' and look for jquey or similar misspellings of jquery
    Affected if The jquey package (any version) is found in the local node_modules

You are affected if the jquey package at version 1.0.1 is present in your node_modules or listed as a dependency, as this malicious typosquat exfiltrates SSH keys and bash history during its installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Immediately remove the jquey package if present in any environment, rotate all SSH keys that may have been present on affected systems, and audit for unauthorized network connections to unknown servers.

Fix this in Jquey Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-16204 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-16204 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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