CVE-2017-16056: Hijacked Environment Variables in mssql.js

mssql.js Updated 02 Oct 2025

Summary

09/11/2018
No i
High
7.5

CVE-2017-16056: mssql.js is malware. Affects mssql.js versions < 1.0.2. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The mssql.js package is an npm package used for interacting with Microsoft SQL Server databases. It provides a JavaScript API for executing queries, managing transactions, and accessing database metadata. This package is vulnerable to a hijacking attack where environment variables are stolen and sent to attacker-controlled locations.

Vulnerability Detail

The vulnerability in mssql.js allows an attacker to steal environment variables from the affected system. These environment variables may contain sensitive information such as database credentials, API keys, or other sensitive data. The attacker can then use this stolen information for malicious purposes, potentially gaining unauthorized access to databases or other systems. The package has been removed from the npm registry to prevent further installations.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround for this vulnerability. It is crucial to follow the recommended steps to fix the issue and mitigate any potential damage.

Conclusion

The mssql.js package is vulnerable to a hijacking attack that allows an attacker to steal environment variables. This can lead to the exposure of sensitive information and potential unauthorized access to databases or other systems. It is crucial to follow the recommended steps to fix the vulnerability and review any potential security breaches. For further support on vulnerability remediation, contact DevNack.com.

See every vulnerability recorded for mssql.js →

Share this vulnerability

FAQ

The attacker exploits this vulnerability by injecting the mssql.js package into the target system. Once installed, the package steals environment variables and sends them to the attacker-controlled locations.

The stolen information can include sensitive data such as database credentials, API keys, or any other information stored in environment variables.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply provide your package-lock.json file, and Vulert will analyze it for any open-source vulnerabilities, including this one.

No, updating the package will not fix this vulnerability as it is a deliberate malicious act. The package has been removed from the npm registry to prevent further installations.

If you find the mssql.js package installed in your environment, you should follow the recommended steps to fix the vulnerability. Additionally, you should investigate how the package got there and review any potential security breaches.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback