CVE-2021-34083: Command Injection in google-it

google-it Updated 02 Oct 2025

Summary

03/06/2022
No i
High
8.1

CVE-2021-34083: Command injection in google-it. Affects google-it versions < 1.6.2. 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 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

google-it is a Node.js package available on npm that allows users to send search queries to Google and receive the results in a JSON format. It provides a convenient way to interact with the Google search engine programmatically. However, versions up to 1.6.2 of google-it are vulnerable to command injection, which can lead to remote code execution (RCE) on the server.

Vulnerability Detail

The vulnerability in google-it arises when using the 'Open in browser' option. In affected versions, the package concatenates the link obtained from Google search results to a shell command without proper sanitization. This can allow an attacker to inject malicious commands and potentially execute arbitrary code on the server. The impact of this vulnerability is high, as it can lead to unauthorized access, data leakage, or even complete compromise of the affected system.

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 a temporary workaround, users can avoid using the 'Open in browser' option in google-it until the package is updated to a secure version. By refraining from using this feature, the risk of command injection and potential RCE can be mitigated.

Conclusion

In conclusion, the google-it package versions up to 1.6.2 are vulnerable to command injection, which can lead to remote code execution. It is crucial to update to a secure version of the package to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for google-it →

Share this vulnerability

FAQ

google-it is a Node.js package that allows users to send search queries to Google and receive the results in a JSON format. It simplifies programmatically interacting with the Google search engine.

Command injection is a security vulnerability that allows an attacker to execute arbitrary commands on a target system. In the case of google-it, the vulnerability arises from unsafely concatenating user-controlled input to a shell command.

The impact of this vulnerability can be severe. An attacker can potentially execute arbitrary code on the server, leading to unauthorized access, data leakage, or complete compromise of the affected system.

To fix this vulnerability, update google-it to a version that includes the necessary security patches. The maintainers have addressed this issue in versions beyond 1.6.2.

As a temporary workaround, avoid using the 'Open in browser' option in google-it until the package is updated. This will help mitigate the risk of command injection and potential remote code execution.

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