CVE-2018-25083: Command Injection Vulnerability in pullit

pullit Updated 02 Oct 2025

Summary

03/09/2020
Yes i
High
Not published

CVE-2018-25083: pullit vulnerable to command injection. Affects pullit versions < 1.4.0. Fixed in 1.4.0. 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

pullit is an npm package used for managing git repositories. It allows users to perform various operations on git branches. However, versions prior to 1.4.0 are vulnerable to Command Injection. This means that the package does not properly validate user input on git branch names and directly concatenates it to an exec call, enabling attackers to execute arbitrary commands on the system.

Vulnerability Detail

The vulnerability in pullit arises from the lack of input validation on git branch names. By exploiting this, an attacker can inject malicious commands that will be executed by the system. This can lead to unauthorized access, data breaches, or even complete compromise of the affected system. The vulnerability has been assigned a severity rating of HIGH (CVSS score not provided) and is classified under CWE-77 (Improper Neutralization of Special Elements used in a Command).

How To Fix

Latest published version: 2.1.0 as of 22 Oct 2026

npm install pullit@2.1.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.4.0

This is the first release that contains the fix.

npm install pullit@1.4.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. However, users can mitigate the risk by ensuring that they only use trusted branch names and avoid accepting user input without proper validation and sanitization.

Conclusion

The pullit package prior to version 1.4.0 is vulnerable to Command Injection, which can lead to unauthorized access, data breaches, or compromise of the affected system. It is crucial to upgrade to the latest version to patch the vulnerability and ensure the security of the system. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for pullit →

Share this vulnerability

FAQ

pullit is an npm package used for managing git repositories. It provides functionality to perform various operations on git branches.

Command Injection is a vulnerability that allows an attacker to execute arbitrary commands on a system by injecting malicious input into a command execution function.

The impact of this vulnerability can be severe, as it allows attackers to execute arbitrary commands on the system. This can lead to unauthorized access, data breaches, or complete compromise of the affected system.

To fix this vulnerability, it is recommended to upgrade to version 1.4.0 or later of the pullit package. This version includes proper input validation to prevent command injection attacks.

While there is no specific workaround mentioned, users can mitigate the risk by ensuring that they only use trusted branch names and avoid accepting user input without proper validation and sanitization.

Related vulnerabilities

Recent vulnerabilities recorded for pullit.

How To Fix

Latest published version: 2.1.0 as of 22 Oct 2026

npm install pullit@2.1.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.4.0

This is the first release that contains the fix.

npm install pullit@1.4.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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