From: "mv" <sdoshi@mvista.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [[kirkstone][meta-oe][PATCH] xterm : Fix CVE-2022-45063 code execution via OSC 50 input sequences] CVE-2022-45063
Date: Thu, 29 Dec 2022 05:11:36 -0800 [thread overview]
Message-ID: <10920.1672319496310011965@lists.openembedded.org> (raw)
In-Reply-To: <20221229125920.567710-1-sdoshi@mvista.com>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
Hi Team,
Even though the patch subject is -> *Subject: [PATCH] snapshot of project "xterm", label xterm-374c,* It fixes CVE-2022-45063 as per -> https://github.com/ThomasDickey/xterm-snapshots/commit/787636674918873a091e7a4ef5977263ba982322#diff-9f51c083fda4d1b957dde3784a2aa3e18afbcb178ed8ecf960380e64ce541089 [file name :xterm.log.html] which states that *
*
{{{
<li>improve error-recovery when setting a bitmap font for the
VT100 window, e.g., in case <em>OSC 50</em> failed,
restoring the most recent valid font so that a subsequent
<em>OSC 50</em> reports this correctly (report by David
Leadbeater).</li>
}}}
Regards,
Siddharth
[-- Attachment #2: Type: text/html, Size: 1153 bytes --]
prev parent reply other threads:[~2022-12-29 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 12:59 [[kirkstone][meta-oe][PATCH] xterm : Fix CVE-2022-45063 code execution via OSC 50 input sequences] CVE-2022-45063 Siddharth
2022-12-29 13:11 ` mv [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=10920.1672319496310011965@lists.openembedded.org \
--to=sdoshi@mvista.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.