CVE-2020-8149: Arbitrary shell command execution in logkitty

logkitty Updated 02 Oct 2025

Summary

05/06/2020
Yes i
Critical
9.8

CVE-2020-8149: Arbitrary shell command execution in logkitty. Affects logkitty versions < 0.7.1. Fixed in 0.7.1. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The logkitty npm package is a logging utility for Node.js applications. It allows developers to capture and analyze logs generated by their applications. The package is widely used in the Node.js ecosystem for debugging and troubleshooting purposes. However, versions prior to 0.7.1 are vulnerable to arbitrary shell command execution.

Vulnerability Detail

The vulnerability in logkitty arises from a lack of output sanitization. This allows an attacker to execute arbitrary shell commands by manipulating the input in a way that is not properly sanitized. By exploiting this vulnerability, an attacker can gain unauthorized access to the underlying system and potentially perform malicious actions. The impact of this vulnerability can range from unauthorized data access to complete system compromise.

How To Fix

Minimum fixed version

0.7.1

This is the first release that contains the fix.

npm install logkitty@0.7.1

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

Workaround

If upgrading to the latest version is not immediately feasible, a temporary workaround is to avoid using the logkitty package or to implement additional input sanitization measures in the application code. This can involve validating and sanitizing user input before passing it to logkitty functions to prevent command injection.

Conclusion

The vulnerability in logkitty allows for arbitrary shell command execution, which can have severe consequences for the affected system. It is crucial to upgrade to the latest version of logkitty or implement appropriate mitigations to prevent exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for logkitty →

Share this vulnerability

FAQ

logkitty is an npm package used for capturing and analyzing logs in Node.js applications.

The vulnerability allows an attacker to execute arbitrary shell commands, potentially leading to unauthorized access or system compromise.

To fix this vulnerability, upgrade to logkitty version 0.7.1 or later.

If upgrading is not immediately feasible, you can avoid using logkitty or implement additional input sanitization measures in your application code.

You can find more information about this vulnerability in the GitHub Security Advisory database.

How To Fix

Minimum fixed version

0.7.1

This is the first release that contains the fix.

npm install logkitty@0.7.1

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