CVE-2020-7629: OS Command Injection in install-package

install-package Updated 02 Oct 2025

Summary

10/02/2022
No i
Critical
9.8

CVE-2020-7629: OS Command Injection in install-package. Affects install-package versions < 0.4.0. 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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The install-package is an npm package used for installing packages in a Node.js project. It provides a convenient way to manage dependencies and install packages from the npm registry. However, versions up to 0.4.0 of install-package are vulnerable to OS Command Injection. This vulnerability allows an attacker to execute arbitrary commands by exploiting the options argument.

Vulnerability Detail

The OS Command Injection vulnerability in install-package arises from improper input validation. An attacker can manipulate the options argument to inject malicious commands, which are then executed by the application. This can lead to various security risks, including unauthorized access, data breaches, and remote code execution. The severity of this vulnerability is rated as CRITICAL with a CVSS score of 9.8.

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

If upgrading to the latest version is not immediately feasible, a temporary workaround is to sanitize and validate the options argument before passing it to the install-package function. This can be done by implementing input validation and filtering techniques to prevent the execution of arbitrary commands.

Conclusion

The OS Command Injection vulnerability in install-package can have severe consequences, including unauthorized access and remote code execution. It is crucial to promptly upgrade to the patched version or apply the recommended workaround to mitigate the risk. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for install-package →

Share this vulnerability

FAQ

install-package is an npm package used for managing dependencies and installing packages in a Node.js project.

OS Command Injection is a vulnerability that allows an attacker to execute arbitrary commands on a target system by injecting malicious commands into an application's command execution mechanism.

This vulnerability can lead to unauthorized access, data breaches, and remote code execution, potentially compromising the security and integrity of the affected system.

To fix this vulnerability, upgrade to version 0.4.1 or later of install-package. Update your package.json file and run the package manager to install the updated package.

A temporary workaround is to sanitize and validate the options argument before passing it to the install-package function. Implement input validation and filtering techniques to prevent the execution of arbitrary commands.

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