Processing commands for cont...@bugs.debian.org:
> retitle 1110769 xterm: segfault in ScrnWriteText with reverseWrap set
Bug #1110769 [xterm] xterm: segfault in ScrnWriteText on 3-byte binary data
Changed Bug title to 'xterm: segfault in ScrnWriteText with reverseWrap set'
from 'xterm: segfault i
On 2025-08-10 20:57:26 -0400, Thomas Dickey wrote:
> Then it's a bug in reverseWrap (not related to allowC1Printable).
Yes. I mentioned allowC1Printable because it was needed with
my first testcase (with xterm 398-1).
> Sure, it's a bug,
>
>reverseWrap (class ReverseWrap)
>
On Mon, Aug 11, 2025 at 02:31:59AM +0200, Vincent Lefevre wrote:
> On 2025-08-10 19:55:33 -0400, Thomas Dickey wrote:
> > On Sun, Aug 10, 2025 at 07:37:18PM -0400, Thomas Dickey wrote:
> > > On Mon, Aug 11, 2025 at 01:09:26AM +0200, Vincent Lefevre wrote:
> > > > Package: xterm
> > > > Version: 398
On 2025-08-10 19:55:33 -0400, Thomas Dickey wrote:
> On Sun, Aug 10, 2025 at 07:37:18PM -0400, Thomas Dickey wrote:
> > On Mon, Aug 11, 2025 at 01:09:26AM +0200, Vincent Lefevre wrote:
> > > Package: xterm
> > > Version: 398-1
> > > Severity: important
> > > Tags: security upstream
> > > X-Debbugs-
Control: clone -1 -2
Control: retitle -2 xterm: allowC1Printable (-k8) does the opposite of what it
says
On 2025-08-11 01:09:26 +0200, Vincent Lefevre wrote:
> An attacker could make an xterm crash by providing such a sequence
> in a text file. It is generally a bad idea to can untrusted and
> un
On Sun, Aug 10, 2025 at 07:37:18PM -0400, Thomas Dickey wrote:
> On Mon, Aug 11, 2025 at 01:09:26AM +0200, Vincent Lefevre wrote:
> > Package: xterm
> > Version: 398-1
> > Severity: important
> > Tags: security upstream
> > X-Debbugs-Cc: Debian Security Team
> >
> > I've just noticed that it is v
On Mon, Aug 11, 2025 at 01:09:26AM +0200, Vincent Lefevre wrote:
> Package: xterm
> Version: 398-1
> Severity: important
> Tags: security upstream
> X-Debbugs-Cc: Debian Security Team
>
> I've just noticed that it is very easy to make xterm crash with
> some binary data:
>
> /usr/bin/xterm -e
On 2025-08-11 01:09:26 +0200, Vincent Lefevre wrote:
> I've just noticed that it is very easy to make xterm crash with
> some binary data:
>
> /usr/bin/xterm -e 'printf "\x9a\x85\x08"; sleep 2'
Something important: this depends on the xterm settings.
One needs the following in the XTerm resourc
Package: xterm
Version: 398-1
Severity: important
Tags: security upstream
X-Debbugs-Cc: Debian Security Team
I've just noticed that it is very easy to make xterm crash with
some binary data:
/usr/bin/xterm -e 'printf "\x9a\x85\x08"; sleep 2'
The backtrace:
$ gdb /usr/bin/xterm core.2173502
[
9 matches
Mail list logo
