Openshift Container PlatformApplication · Redhat
CVE-2019-0542
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA remote code execution vulnerability exists in Xterm.js when the component mishandles special characters, aka "Xterm Remote Code Execution Vulnerability." This affects xterm.js.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA remote code execution vulnerability exists in xterm.js when the component mishandles special characters. The vulnerability allows attackers to execute arbitrary code through maliciously crafted escape sequences or character sequences processed by the terminal emulator.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Openshift Container PlatformApplication
>= 3.9, < 3.9.99>= 3.10, < 3.10.163> 3.11, < 3.11.104< 5.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if xterm.js is in useSearch for xterm.js in your project dependencies (package.json, package-lock.json, yarn.lock, or node_modules/xterm directory)Affected if xterm.js is present in your dependencies or installed packages
-
Check xterm.js versionRun npm list xterm or grep -r '"xterm"' package.json to retrieve the installed version numberAffected if The installed version is earlier than 5.0.0 (e.g., 4.x, 3.x, etc.)
-
Check if running Red Hat Openshift Container PlatformRun oc version or check for OCP-specific configuration files and cluster version with oc get clusterversionAffected if Openshift Container Platform is deployed and the version falls within 3.9 to 3.9.99, 3.10 to 3.10.163, or 3.11 to 3.11.104
-
Verify terminal component is activeInspect web console or API responses for terminal/console functionality - check if the xterm.js library is being loaded and initialized in the browser or frontend logsAffected if The terminal emulator feature is enabled and actively processing input/output through xterm.js
Your environment is affected if xterm.js version is below 5.0.0 OR you run Openshift Container Platform versions 3.9.x, 3.10.x through 3.10.163, or 3.11.x through 3.11.104, and the terminal emulator component is actively in use.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data3.9.993.10.1633.11.104
Upgrade xterm.js to the patched version. Additionally, implement input validation and sanitization on the backend before rendering content in the terminal, and ensure shell processes run with minimal privileges.
Fix this in Openshift Container Platform
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-0542 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-0542 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data