CVE-2014-3741: Command Injection in printer

printer Updated 02 Oct 2025

Summary

28/11/2017
Yes i
Critical
9.8

CVE-2014-3741: Potential Command Injection in printer. Affects printer versions < 0.0.2. Fixed in 0.0.2. 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 printer package is an npm package used for printing documents. It provides functionality to print directly from a Node.js application. The package is vulnerable to a command injection vulnerability in versions 0.0.1 and earlier. This vulnerability arises due to improper sanitization of command arguments in the printDirect() function.

Vulnerability Detail

The command injection vulnerability in the printer package allows an attacker to execute arbitrary commands on the system where the vulnerable package is installed. By exploiting this vulnerability, an attacker can pass malicious input as command arguments, leading to the execution of unintended commands with the privileges of the application or user executing the printer package. This can result in unauthorized access, data loss, or further compromise of the system.

How To Fix

Latest published version: 0.4.0 as of 22 Oct 2026

npm install printer@0.4.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

0.0.2

This is the first release that contains the fix.

npm install printer@0.0.2

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.

Conclusion

The printer package versions 0.0.1 and earlier are vulnerable to a command injection vulnerability. To mitigate this vulnerability, it is recommended to update to version 0.0.2 or later. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for printer →

Share this vulnerability

FAQ

The vulnerability allows an attacker to execute arbitrary commands on the system, potentially leading to unauthorized access, data loss, or further compromise.

Versions 0.0.1 and earlier of the printer package are affected.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities using package-lock.json.

Yes, the CVSS score for this vulnerability is 9.8, indicating a critical severity.

There are no known exploits mentioned for this vulnerability.

How To Fix

Latest published version: 0.4.0 as of 22 Oct 2026

npm install printer@0.4.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

0.0.2

This is the first release that contains the fix.

npm install printer@0.0.2

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