blob: d17ced80428dd9ae2541e90d0cd91694584fab42 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="202211-09">
<title>xterm: Arbitrary Code Execution</title>
<synopsis>A vulnerability has been found in xterm which could allow for arbitrary code execution.</synopsis>
<product type="ebuild">xterm</product>
<announced>2022-11-22</announced>
<revised count="1">2022-11-22</revised>
<bug>880747</bug>
<access>remote</access>
<affected>
<package name="x11-terms/xterm" auto="yes" arch="*">
<unaffected range="ge">375</unaffected>
<vulnerable range="lt">375</vulnerable>
</package>
</affected>
<background>
<p>xterm is a terminal emulator for the X Window system.</p>
</background>
<description>
<p>xterm does not correctly handle control characters related to OSC 50 font ops sequence handling.</p>
</description>
<impact type="normal">
<p>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.</p>
</impact>
<workaround>
<p>As a workaround, users can disable xterm's usage of OSC 50 sequences by adding the following to the XResources configuration:
XTerm*allowFontOps: false</p>
</workaround>
<resolution>
<p>All xterm users should upgrade to the latest version:</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=x11-terms/xterm-375"
</code>
</resolution>
<references>
<uri link="https://nvd.nist.gov/vuln/detail/CVE-2022-45063">CVE-2022-45063</uri>
</references>
<metadata tag="requester" timestamp="2022-11-22T03:53:08.351235Z">ajak</metadata>
<metadata tag="submitter" timestamp="2022-11-22T03:53:08.356875Z">ajak</metadata>
</glsa>
|