Xterm.js Remote Code Execution Vulnerability (CVE-2019-0542)

node-xterm Updated 02 Oct 2025

Summary

09/01/2019
N/A
Yes i
High
8.8

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 across 2 version ranges.

< 3.8.1-1 < 904ddffc8d370421783f0917797617bfce508854

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

Xterm.js is a popular JavaScript library that provides a terminal emulator for web applications. It allows users to interact with command-line interfaces within a browser environment. However, a vulnerability has been discovered in Xterm.js that could potentially allow remote code execution.

Vulnerability Detail

The vulnerability in Xterm.js arises from mishandling special characters. An attacker could exploit this flaw to execute arbitrary code remotely, potentially leading to unauthorized access, data breaches, or further compromise of the affected system. The vulnerability has been assigned the CVE identifier CVE-2019-0542 and has a CVSS score of 8.8, indicating a high severity.

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

As a temporary workaround, users can disable or restrict access to the affected functionality in Xterm.js until the package can be updated. This can be achieved by modifying the code or configuration to prevent the execution of potentially malicious commands.

Conclusion

The Xterm.js Remote Code Execution Vulnerability (CVE-2019-0542) is a critical security issue that could allow attackers to execute arbitrary code remotely. It is crucial to update the affected package to version 3.8.1-1 or later to mitigate the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for node-xterm →

Share this vulnerability

FAQ

Xterm.js is a JavaScript library that provides a terminal emulator for web applications, allowing users to interact with command-line interfaces within a browser environment.

The vulnerability in Xterm.js could allow remote code execution, potentially leading to unauthorized access, data breaches, or further compromise of the affected system.

To fix this vulnerability, update the affected package to version 3.8.1-1 or later, which includes a patch that addresses the issue.

As a temporary workaround, you can disable or restrict access to the affected functionality in Xterm.js until the package can be updated.

The CVSS score of this vulnerability is 8.8, indicating a high severity.

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