portage-ng / portage / x11-terms / xterm / 410
portage-ng glsa
4 advisories reference x11-terms/xterm · none place version 410 in a vulnerable range
▸ GLSA 202211-09 xterm: Arbitrary Code Execution this version unaffected normal remote 2022-11-22

A vulnerability has been found in xterm which could allow for arbitrary code execution.

Announced
2022-11-22
Revised
2022-11-22
Access
remote
Bugs
#880747
Advisory
https://security.gentoo.org/glsa/202211-09

Affected packages

PackageArchVulnerableUnaffected
x11-terms/xterm*< 375>= 375

Background

xterm is a terminal emulator for the X Window system.

Description

xterm does not correctly handle control characters related to OSC 50 font ops sequence handling.

Impact

The vulnerability allows text written to the terminal to write text to the terminal's command line. If the terminal's shell is zsh running with vi line editing mode, text written to the terminal can also trigger the execution of arbitrary commands via writing ^G to the terminal.

Workaround

As a workaround, users can disable xterm's usage of OSC 50 sequences by adding the following to the XResources configuration: XTerm*allowFontOps: false

Resolution

All xterm users should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-terms/xterm-375"

References

▸ GLSA 202208-22 xterm: Multiple Vulnerabilities this version unaffected low remote 2022-08-14

Multiple vulnerabilities have been discovered in xterm, the worst of which could result in denial of service.

Announced
2022-08-14
Revised
2022-08-14
Access
remote
Bugs
#769839 #832409
Advisory
https://security.gentoo.org/glsa/202208-22

Affected packages

PackageArchVulnerableUnaffected
x11-terms/xterm*< 371>= 371

Background

xterm is a terminal emulator for the X Window system.

Description

Multiple vulnerabilities have been discovered in xterm. Please review the CVE identifiers referenced below for details.

Impact

Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

Resolution

All xterm users should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-terms/xterm-371"

References

▸ GLSA 200902-04 xterm: User-assisted arbitrary commands execution this version unaffected normal remote 2009-02-12

An error in the processing of special sequences in xterm may lead to arbitrary commands execution.

Announced
2009-02-12
Revised
2009-02-12
Access
remote
Bugs
#253155
Advisory
https://security.gentoo.org/glsa/200902-04

Affected packages

PackageArchVulnerableUnaffected
x11-terms/xterm*< 239>= 239

Background

xterm is a terminal emulator for the X Window system.

Description

Paul Szabo reported an insufficient input sanitization when processing Device Control Request Status String (DECRQSS) sequences.

Impact

A remote attacker could entice a user to display a file containing specially crafted DECRQSS sequences, possibly resulting in the remote execution of arbitrary commands with the privileges of the user viewing the file.

Workaround

There is no known workaround at this time.

Resolution

All xterm users should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-terms/xterm-239"

References

▸ GLSA 200608-25 X.org and some X.org libraries: Local privilege escalations this version unaffected high local 2006-08-28

X.org, libX11, xdm, xf86dga, xinit, xload, xtrans, and xterm are vulnerable to local privilege escalations because of unchecked setuid() calls.

Announced
2006-08-28
Revised
2006-12-13 (revision 2)
Access
local
Bugs
#135974
Advisory
https://security.gentoo.org/glsa/200608-25

Affected packages

PackageArchVulnerableUnaffected
app-emulation/emul-linux-x86-xlibsamd64< 7.0-r2>= 7.0-r2
x11-apps/xdm*< 1.0.4-r1>= 1.0.4-r1
x11-apps/xf86dga*< 1.0.1-r1>= 1.0.1-r1
x11-apps/xinit*< 1.0.2-r6>= 1.0.2-r6
x11-apps/xload*< 1.0.1-r1>= 1.0.1-r1
x11-base/xorg-server*< 1.1.0-r1>= 1.0.2-r6 (revision), >= 1.1.0-r1
x11-base/xorg-x11*< 6.9.0-r2>= 6.8.2-r8 (revision), >= 6.9.0-r2
x11-libs/libx11*< 1.0.1-r1>= 1.0.1-r1
x11-libs/xtrans*< 1.0.0-r1>= 1.0.0-r1
x11-terms/xterm*< 215>= 215

Background

X.org is an implementation of the X Window System.

Description

Several X.org libraries and X.org itself contain system calls to set*uid() functions, without checking their result.

Impact

Local users could deliberately exceed their assigned resource limits and elevate their privileges after an unsuccessful set*uid() system call. This requires resource limits to be enabled on the machine.

Workaround

There is no known workaround at this time.

Resolution

All X.Org xdm users should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-apps/xdm-1.0.4-r1"

All X.Org xinit users should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-apps/xinit-1.0.2-r6"

All X.Org xload users should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-apps/xload-1.0.1-r1"

All X.Org xf86dga users should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-apps/xf86dga-1.0.1-r1"

All X.Org users should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-base/xorg-x11-6.9.0-r2"

All X.Org X servers users should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-base/xorg-server-1.1.0-r1"

All X.Org X11 library users should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-libs/libx11-1.0.1-r1"

All X.Org xtrans library users should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-libs/xtrans-1.0.1-r1"

All xterm users should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-terms/xterm-215"

All users of the X11R6 libraries for emulation of 32bit x86 on amd64 should upgrade to the latest version:

# emerge --sync
# emerge --ask --oneshot --verbose ">=app-emulation/emul-linux-x86-xlibs-7.0-r2"

Please note that the fixed packages have been available for most architectures since June 30th but the GLSA release was held up waiting for the remaining architectures.

References