xterm: CVE-2022-24130

Debian Bug report logs - #1004689
xterm: CVE-2022-24130

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Salvatore Bonaccorso <carnil@debian.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: xterm: CVE-2022-24130

Date: Mon, 31 Jan 2022 20:37:03 +0100

Source: xterm
Version: 370-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org>

Hi,

The following vulnerability was published for xterm.

CVE-2022-24130[0]:
| 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.


If you fix the vulnerability please also make sure to include the
CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

For further information see:

[0] https://security-tracker.debian.org/tracker/CVE-2022-24130
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24130
[1] https://www.openwall.com/lists/oss-security/2022/01/30/2
[3] https://www.openwall.com/lists/oss-security/2022/01/30/3

Please adjust the affected versions in the BTS as needed.

Regards,
Salvatore

Message #16 received at 1004689@bugs.debian.org (full text, mbox, reply):

From: Thomas Dickey <dickey@his.com>

To: 1004689@bugs.debian.org

Subject: Re: Bug#1004689: xterm: CVE-2022-24130

Date: Mon, 31 Jan 2022 20:17:22 -0500

[Message part 1 (text/plain, inline)]

On Mon, Jan 31, 2022 at 08:37:03PM +0100, Salvatore Bonaccorso wrote:
> Source: xterm
> Version: 370-1
> Severity: important
> Tags: security upstream
> X-Debbugs-Cc: carnil@debian.org, Debian Security Team <team@security.debian.org>
> 
> Hi,
> 
> The following vulnerability was published for xterm.
> 
> CVE-2022-24130[0]:
> | 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.
> 
> 
> If you fix the vulnerability please also make sure to include the
> CVE (Common Vulnerabilities & Exposures) id in your changelog entry.

changelog as usual reflects the actual report, not a succession of
secondhand information.

I applied a fix for the issue yesterday, which will be in #371.
For backports, do as suggested here:

http://cvsweb.netbsd.org/bsdweb.cgi/pkgsrc/x11/xterm/patches/patch-graphics__sixel.c

derived from

https://github.com/ThomasDickey/xterm-snapshots/blob/master/graphics_sixel.c

-- 
Thomas E. Dickey <dickey@invisible-island.net>
https://invisible-island.net
ftp://ftp.invisible-island.net

[signature.asc (application/pgp-signature, inline)]

Send a report that this bug log contains spam.