dbcve.org
NodemssqlDatabase / datastore · Nodemssql Project

CVE-2017-16057

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
nodemssql was a malicious module published with the intent to hijack environment variables. It has been unpublished by npm.

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

nodemssql was a malicious npm module designed to exfiltrate environment variables (containing sensitive data like API keys, credentials, and secrets) from the host system. It represents a supply chain attack via a compromised/trojaned package published to the public npm registry.

MitigationAudit dependency trees for nodemssql presence and remove if found. Review recently added dependencies and implement package integrity verification (e.g., npm audit, lockfile analysis) to detect malicious packages.

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
NodemssqlDatabase / datastore
Affected:all versions

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. Search package.json for nodemssql dependency
    Inspect your project's package.json file and search for 'nodemssql' in the dependencies, devDependencies, or peerDependencies sections
    Affected if nodemssql appears in any dependencies section
  2. Inspect node_modules directory for nodemssql
    Check if the nodemssql directory exists within node_modules in your project root or any nested node_modules folders
    Affected if The nodemssql folder exists in node_modules
  3. Check lockfile for nodemssql reference
    Examine your package-lock.json or npm-shrinkwrap.json file for any entries referencing 'nodemssql'
    Affected if nodemssql appears in the lockfile dependencies
  4. Scan nested dependencies for nodemssql
    Run 'npm ls nodemssql' or 'npm ls --all' to check if nodemssql is present as a transitive dependency
    Affected if npm ls shows nodemssql in the dependency tree

If nodemssql is found in any form (direct dependency, transitive dependency, or installed in node_modules), the environment is affected by this supply chain attack.

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

Audit dependency trees for nodemssql presence and remove if found. Review recently added dependencies and implement package integrity verification (e.g., npm audit, lockfile analysis) to detect malicious packages.

Fix this in Nodemssql Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-16057 — 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-16057 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