xterm before 380 supports ReGIS reporting for character-set names even if they have unexpected characters (i.e., neither alphanumeric nor underscore), aka a pointer/overflow issue. This can only occur for xterm installations that are configured at compile time to use a certain ex...
Product
ubuntu/xterm vulnerabilities
4 published CVES affecting ubuntu/xterm, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 4
- Critical
- 3
- High
- 0
- Medium
- 1
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest ubuntu/xterm CVEs
Newest publication first
-
CriticalCVSS 9.8 EPSS 0.86%
-
CriticalCVSS 9.8 EPSS 6.6%
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.
-
MediumCVSS 5.5 EPSS 1.7%
xterm through Patch 370, when Sixel support is enabled, allows attackers to trigger a buffer overflow in set_sixel in graphics_sixel.c via crafted text.
-
CriticalCVSS 9.8 EPSS 7.9%
xterm before Patch #366 allows remote attackers to execute arbitrary code or cause a denial of service (segmentation fault) via a crafted UTF-8 combining character sequence.
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.