mssql.js vulnerabilities and fixes

Recent CVEs affecting mssql.js, with upgrade or downgrade steps. 1 tracked.

Also searched as: mssql js, mssqljs.

mssql.js has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2018-06-07. Highest priority: CVE-2017-16056 (score 48/100).

• CVE-2017-16056 HIGH 7.5 MITIGATE mssql.js was a malicious module published with the intent to hijack environment variables

FAQ

How do I fix mssql.js vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is mssql.js being exploited right now?

None of the tracked mssql.js CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which mssql.js CVE should I patch first?

CVE-2017-16056 currently ranks highest (48/100): mssql.js was a malicious module published with the intent to hijack environment variables.

← Back to latest CVEs