Remote Code Execution Vulnerability in Node-xterm Package

node-xterm Updated 02 Oct 2025

Summary

09/01/2019
N/A
Yes i
Unrated
Not published

DEBIAN-CVE-2019-0542: A remote code execution vulnerability exists in Xterm.js when the component mishandles special characters, aka "Xterm Remote Code Execution Vulnerability." This affects xterm.js. Affects node-xterm versions < 3.8.1-1. Fixed in 3.8.1-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 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

Node-xterm is a popular terminal emulator for web applications, built using JavaScript. It provides a rich set of features for terminal emulation, including support for various terminal protocols and customizable appearance. However, it has been identified to have a critical vulnerability that could allow remote code execution due to mishandling of special characters.

Vulnerability Detail

A remote code execution vulnerability exists in Xterm.js when the component mishandles special characters, allowing attackers to execute arbitrary code on the server or client-side. This vulnerability, identified as DEBIAN-CVE-2019-0542, can lead to severe security breaches, including unauthorized access to sensitive data and system control. The issue arises from improper validation of input, making it susceptible to crafted input that exploits this flaw.

How To Fix

Minimum fixed version

3.8.1-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade node-xterm

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

Workaround

If immediate patching is not feasible, consider implementing input validation to sanitize special characters before processing them in the application. This can help mitigate the risk of exploitation until the package is updated.

Conclusion

The remote code execution vulnerability in the node-xterm package poses significant security risks. It is crucial to update to the patched version 3.8.1-1 to mitigate these risks. Additionally, utilizing input validation can serve as a temporary measure to protect against potential exploitation.

See every vulnerability recorded for node-xterm →

Share this vulnerability

FAQ

The vulnerability allows remote code execution due to mishandling of special characters in the Xterm.js component.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Exploitation of this vulnerability can lead to unauthorized access, data breaches, and control over the affected system.

Yes, the patched version of the node-xterm package is 3.8.1-1. Updating to this version will resolve the vulnerability.

Implement input validation to sanitize special characters as a temporary workaround until the package can be updated.

Related vulnerabilities

Recent vulnerabilities recorded for node-xterm.

How To Fix

Minimum fixed version

3.8.1-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade node-xterm

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