From: lux <lx@shellcodes.org>
To: Robert Pluim <rpluim@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 63063@debbugs.gnu.org, fuo@fuo.fi
Subject: bug#63063: CVE-2021-36699 report
Date: Wed, 26 Apr 2023 00:37:33 +0800 [thread overview]
Message-ID: <tencent_B014E537C281836B39DF67A66AD66B1EEF09@qq.com> (raw)
In-Reply-To: <87mt2w7x7v.fsf@gmail.com>
On Tue, 2023-04-25 at 18:17 +0200, Robert Pluim wrote:
> > > > > > On Tue, 25 Apr 2023 19:01:47 +0300, Eli Zaretskii
> > > > > > <eliz@gnu.org> said:
>
> >> From: lux <lx@shellcodes.org>
> >> Cc: 63063@debbugs.gnu.org, fuo@fuo.fi
> >> Date: Tue, 25 Apr 2023 23:54:33 +0800
> >>
> >> I think if the reported CVEs are real and valid, they should
> be taken
> >> seriously.
>
> Eli> I agree, but in this case all I see is a convoluted way of
> having
> Eli> Emacs crash. That's not a security problem in my book.
>
> "Itʼs a denial of service attack. You MUST fix it. Whereʼs my fee?"
>
> (sorry, I too deal with this kind of stuff far too often).
>
> Robert
I have to face this problem every day.
Yes, I'm faced with many meaningless CVE numbers every day.
So I hope the submitter will give the details and the developer will
decide to ignore, fix urgently, or postpone the fix depending on the
level of harm.
next prev parent reply other threads:[~2023-04-25 16:37 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <40-63e3c600-3-2d802d00@111202636>
[not found] ` <01070187b503303f-1657dcaa-4f53-47da-9679-2f68a682d447-000000@eu-central-1.amazonses.com>
[not found] ` <bcb96279c47143f403f588dc3f020725029137bd.camel@josefsson.org>
2023-04-24 21:27 ` CVE-2021-36699 report fuomag9
2023-04-25 7:14 ` bug#63063: " Eli Zaretskii
2023-04-25 7:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-25 7:55 ` Eli Zaretskii
2023-04-25 8:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-25 9:09 ` Eli Zaretskii
2023-04-25 10:55 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-25 11:51 ` Eli Zaretskii
2023-04-25 12:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-25 12:47 ` Eli Zaretskii
2023-04-25 12:59 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-25 13:06 ` Eli Zaretskii
2023-04-25 13:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-25 15:54 ` lux
2023-04-25 16:01 ` Eli Zaretskii
2023-04-25 16:17 ` Robert Pluim
2023-04-25 16:37 ` lux [this message]
2023-04-26 1:28 ` Richard Stallman
2023-04-25 8:45 ` fuomag9 via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <874jp4ecg6.fsf@yahoo.com>
[not found] ` <87o7nc77tt.fsf@valhala.localdomain>
2023-04-25 7:53 ` Eli Zaretskii
[not found] ` <87zg6wctqg.fsf@yahoo.com>
2023-04-25 7:53 ` Eli Zaretskii
[not found] ` <CAP_d_8VnxkBOZ3xwccB_URY7vnSCEA2f7ysXOneiwgLHiLEiiA@mail.gmail.com>
2023-04-25 7:57 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=tencent_B014E537C281836B39DF67A66AD66B1EEF09@qq.com \
--to=lx@shellcodes.org \
--cc=63063@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=fuo@fuo.fi \
--cc=luangruo@yahoo.com \
--cc=rpluim@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).