Skip to content
Fencer Vulns
critical 9.8

CVE-2022-45063 json

xterm before 375 allows code execution via font ops, e.g., because an OSC 50 response may have Ctrl-g and therefore lead to command executi…

published 2022-11-10 3 y ago modified 2026-06-17 4 mo ago also EUVD-2022-47985

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
6.6%
EPSS 6.6% chance of exploitation in 30 days, percentile 93%
public exploits
0
none known

Summary

xterm before 375 allows code execution via font ops, e.g., because an OSC 50 response may have Ctrl-g and therefore lead to command execution within the vi line-editing mode of Zsh. NOTE: font ops are not allowed in the xterm default configurations of some Linux distributions.

Patch / fix

  • invisible-island xterm 375
  • xterm Debian 14, Debian 13, Debian 12 375-1

debian advisories DEBIAN-CVE-2022-45063

  • xterm RHEL 9 366-10.el9_6
  • xterm-resize RHEL 9 366-10.el9_6

red hat advisories RHSA-2025:7427

  • xterm SLES for SAP 12 SP5, SLES for SAP 12 SP4, SLES 12 SP5 +5 more 308-5.9.1
  • xterm SLES for SAP 15 SP3, SLES for SAP 15 SP2, SLES 15 SP3-LTSS +12 more 330-150200.11.9.1
  • xterm SLES for SAP 15 SP1, SLES 15 SP1-LTSS, SLE High Performance Computing 15 SP1-LTSS +1 more 330-150000.4.6.1

suse advisories SUSE-SU-2023:0582-1SUSE-SU-2023:0221-1SUSE-SU-2023:0173-1

  • xterm openSUSE Tumbleweed 375-2.1

opensuse advisories openSUSE-SU-2024:12505-1

  • xterm AlmaLinux 9 366-10.el9_6
  • xterm-resize AlmaLinux 9 366-10.el9_6

almalinux advisories ALSA-2025:7427

  • xterm Rocky Linux 9 366-10.el9_6

rocky linux advisories RLSA-2025:7427

  • xterm CBL-Mariner 2.0 380-1

azure linux advisories AZL-11429

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-45063 updated cvss 7.4

xterm: code execution via OSC 50 input sequences

  • Red Hat Enterprise Linux 8 xterm, xterm-resize
    affected: no fix planned “Will not fix”
  • Red Hat OpenShift Container Platform 3.11 openshift3/ose-console
    affected: no fix planned “Out of support scope”
  • Red Hat OpenShift Virtualization 4 container-native-virtualization/kubevirt-console-plugin
    affected: no fix available
  • Red Hat Enterprise Linux AppStream (v. 9) xterm 366-10.el9_6, xterm-resize 366-10.el9_6
    fixed: vendor fix RHSA-2025:7427
  • Red Hat Enterprise Linux AppStream E4S (v.9.4) xterm 366-9.el9_4.1, xterm-resize 366-9.el9_4.1
    fixed: vendor fix RHSA-2026:92418
  • Red Hat Enterprise Linux 6 xterm Red Hat Enterprise Linux 7 xterm Red Hat Enterprise Linux 8 cockpit, cockpit-ws, cockpit-pcp, cockpit-bridge, cockpit-podman, cockpit-system, +5 more Red Hat Enterprise Linux 9 cockpit, cockpit-ws, cockpit-pcp, cockpit-bridge, cockpit-podman, cockpit-system, +5 more Red Hat OpenShift Container Platform 4 openshift4/ose-console Red Hat Virtualization 4 ovirt-web-ui
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
2 y ago

Exploit prediction

6.56% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • news.ycombinator.com https://news.ycombinator.com/item?id=33546415 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Classification

Weakness
  • CWE-77 Improper Neutralization of Special Elements used in a Command

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.