From: Max Nikulin <manikulin@gmail.com>
To: Sean Whitton <spwhitton@spwhitton.name>,
Salvatore Bonaccorso <carnil@debian.org>
Cc: oss-security@lists.openwall.com, emacs@packages.debian.org,
emacs-devel@gnu.org, Ihor Radchenko <yantar92@posteo.net>
Subject: Re: Is CVE-2024-30203 bogus? (Emacs)
Date: Thu, 11 Apr 2024 17:38:48 +0700 [thread overview]
Message-ID: <29c2fa7d-febb-4496-bac7-a963998d7bcb@gmail.com> (raw)
In-Reply-To: <87y19kcle1.fsf@melete.silentflame.com>
On 11/04/2024 16:13, Sean Whitton wrote:
> On Wed 10 Apr 2024 at 04:17pm +02, Salvatore Bonaccorso wrote:
>
>> Note that the CVE assignment (by MITRE as assigning CNA) for
>> CVE-2024-30203 is explicitly as follows:
>>
>>> In Emacs before 29.3, Gnus treats inline MIME contents as trusted.
>>
>> https://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-29&id=937b9042ad7426acdcca33e3d931d8f495bdd804
>
> This commit doesn't fix anything at all, just fyi.
This Emacs commit
2024-02-20 12:44:30 +0300 Ihor Radchenko:
* lisp/gnus/mm-view.el (mm-display-inline-fontify): Mark contents
untrusted.)
is not enough to fix the issue. More changes are required to make the
fix effective, namely
ccc188fcf98 2024-02-20 12:43:51 +0300 Ihor Radchenko: * lisp/files.el
(untrusted-content): New variable.
6f9ea396f49 2024-02-20 12:47:24 +0300 Ihor Radchenko: org-latex-preview:
Add protection when `untrusted-content' is non-nil
When external Org mode is loaded, that version should contain
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=03635a335
2024-02-20 12:47:24 +0300 Ihor Radchenko: org-latex-preview: Add
protection when `untrusted-content' is non-nil
besides Emacs commits ccc188fcf98 and 937b9042ad7
Emacs commit 6f9ea396f49 (fix of built-in Org mode) is currently
associated with CVE-2024-30203, however Org mode commit 03635a335
is not.
prev parent reply other threads:[~2024-04-11 10:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 7:05 Is CVE-2024-30203 bogus? Sean Whitton
2024-04-08 11:38 ` Eli Zaretskii
2024-04-08 16:55 ` Max Nikulin
2024-04-08 18:44 ` Ihor Radchenko
2024-04-10 11:57 ` Is CVE-2024-30203 bogus? (Emacs) Sean Whitton
2024-04-10 12:04 ` Ihor Radchenko
2024-04-10 14:17 ` Salvatore Bonaccorso
2024-04-10 15:07 ` Max Nikulin
2024-04-11 9:12 ` Sean Whitton
2024-04-11 9:13 ` [oss-security] " Sean Whitton
2024-04-11 10:38 ` Max Nikulin [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
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=29c2fa7d-febb-4496-bac7-a963998d7bcb@gmail.com \
--to=manikulin@gmail.com \
--cc=carnil@debian.org \
--cc=emacs-devel@gnu.org \
--cc=emacs@packages.debian.org \
--cc=oss-security@lists.openwall.com \
--cc=spwhitton@spwhitton.name \
--cc=yantar92@posteo.net \
/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).