all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 63063@debbugs.gnu.org, fuo@fuo.fi
Subject: bug#63063: CVE-2021-36699 report
Date: Tue, 25 Apr 2023 10:55:36 +0300	[thread overview]
Message-ID: <83fs8owg3r.fsf@gnu.org> (raw)
In-Reply-To: <87v8hkctlc.fsf@yahoo.com> (message from Po Lu on Tue, 25 Apr 2023 15:24:31 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: fuomag9 <fuo@fuo.fi>,  63063@debbugs.gnu.org
> Date: Tue, 25 Apr 2023 15:24:31 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > Please tell more about the buffer overflow: where does it happen in
> > the Emacs sources, which buffer overflows, and why.  I cannot find
> > these details in your report.
> 
> It happens because the dump file is deliberately edited to be invalid.

I didn't ask about the root cause, I asked about the details of the
problem: where it happens in our sources, and what exactly happens.

> It is not a dump file that Emacs will generate under any circumstance,
> and as such it's not a bug; by the same means, a pointer to an invalid
> Lisp object could be created, causing a similar crash.  Emacs is not
> expected to operate from a corrupt dump file any more than it is
> expected to operate from a corrupt executable.

Noted.  But please let me make up my own mind about this issue, once I
understand the details.  OK?





  reply	other threads:[~2023-04-25  7:55 UTC|newest]

Thread overview: 28+ 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  5:51       ` Po Lu
2023-04-25  7:13         ` Nicolas Martyanoff
2023-04-25  7:21           ` Po Lu
2023-04-25  7:53             ` bug#63063: " Eli Zaretskii
2023-04-25  7:53           ` Eli Zaretskii
2023-04-25  6:37       ` tomas
2023-04-25  7:11         ` Eli Zaretskii
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 [this message]
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
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
2023-04-25  7:40       ` Yuri Khan
2023-04-25  7:57         ` bug#63063: " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83fs8owg3r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=63063@debbugs.gnu.org \
    --cc=fuo@fuo.fi \
    --cc=luangruo@yahoo.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.