CVE-2020-7781: Command Injection in connection-tester
Summary
CVE-2020-7781: Command injection in connection-tester. Affects connection-tester versions < 0.2.1. Fixed in 0.2.1. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The connection-tester package is an npm package used for testing network connectivity. It provides a simple way to check if a connection can be established to a given host and port. The package is commonly used in network monitoring and troubleshooting applications. However, versions before 0.2.1 are vulnerable to command injection.
Vulnerability Detail
The vulnerability in connection-tester allows an attacker to inject arbitrary commands into the system. This occurs due to improper input sanitization in the index.js file at line 15. An attacker can exploit this vulnerability by providing malicious input that gets executed as a command on the host system. This can lead to various consequences, including unauthorized access, data leakage, and remote code execution.
How To Fix
Minimum fixed version
0.2.1
This is the first release that contains the fix.
npm install connection-tester@0.2.1Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version of the connection-tester package to mitigate the risk.
Conclusion
The command injection vulnerability in connection-tester can lead to severe security risks. It is crucial to upgrade to version 0.2.1 or later to mitigate this vulnerability. For further assistance, contact DevNack.com.
See every vulnerability recorded for connection-tester →
FAQ
Connection-tester is an npm package used for testing network connectivity.
Command injection is a security vulnerability that allows an attacker to execute arbitrary commands on a host system.
The consequences of this vulnerability can include unauthorized access, data leakage, and remote code execution.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your package-lock.json file and Vulert will provide real-time alerts for open-source vulnerabilities.
For further support on vulnerability remediation, you can contact info@devnack.com.
