CVE-2019-5485: Command Injection in gitlabhook

gitlabhook Updated 02 Oct 2025

Summary

16/09/2019
No i
Critical
10.0

CVE-2019-5485: Command Injection in gitlabhook. Affects gitlabhook versions < 0.0.17. 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

gitlabhook is an npm package used for integrating GitLab webhooks with Node.js applications. It allows developers to receive and process GitLab webhook events. However, all versions of gitlabhook are vulnerable to Command Injection. The package fails to validate input in the body of a POST request, which is then concatenated to an exec call. This allows attackers to execute arbitrary commands on the system.

Vulnerability Detail

The Command Injection vulnerability in gitlabhook arises due to the lack of input validation. Attackers can exploit this vulnerability by sending a specially crafted POST request with malicious commands in the body. These commands will be executed by the system, potentially leading to unauthorized access, data leakage, or further compromise of the system. The severity of this vulnerability is rated as CRITICAL with a CVSS score of 10.0.

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

As there is no fix available, a possible workaround is to implement strict input validation and sanitization of the body of POST requests in your application code. This can help mitigate the risk of command injection attacks.

Conclusion

gitlabhook is vulnerable to Command Injection, which allows attackers to execute arbitrary commands on the system. Currently, there is no fix available for this vulnerability. It is recommended to consider using an alternative package until a fix is provided. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for gitlabhook →

Share this vulnerability

FAQ

gitlabhook is an npm package used for integrating GitLab webhooks with Node.js applications. It allows developers to receive and process GitLab webhook events.

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

This vulnerability can be exploited by sending a specially crafted POST request to a vulnerable application that uses gitlabhook. The attacker can include malicious commands in the body of the request, which will be executed by the system.

The consequences of this vulnerability can include unauthorized access to sensitive information, data leakage, and further compromise of the system. Attackers can execute arbitrary commands with the privileges of the application or user running the vulnerable code.

Currently, there is no fix available for this vulnerability. It is recommended to consider using an alternative package until a fix is provided.

Related vulnerabilities

Recent vulnerabilities recorded for gitlabhook.

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