From: Sean Whitton <spwhitton@spwhitton.name>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs@packages.debian.org, emacs-devel@gnu.org,
oss-security@lists.openwall.com
Subject: Is CVE-2024-30203 bogus?
Date: Mon, 08 Apr 2024 15:05:21 +0800 [thread overview]
Message-ID: <874jccjpvy.fsf@melete.silentflame.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
Hello Ihor,
The description for CVE-2024-30203 is
In Emacs before 29.3, Gnus treats inline MIME contents as trusted.
and for CVE-2024-30204 is
In Emacs before 29.3, LaTeX preview is enabled by default for e-mail
attachments.
but I think these commits
* ccc188fcf98..: Ihor Radchenko 2024-02-20 * lisp/files.el
(untrusted-content): New variable.
* 937b9042ad7..: Ihor Radchenko 2024-02-20 * lisp/gnus/mm-view.el
(mm-display-inline-fontify): Mark contents untrusted.
* 6f9ea396f49..: Ihor Radchenko 2024-02-20 org-latex-preview: Add
protection when `untrusted-content' is non-nil
fix only a single problem, right? But we have two CVEs.
It seems to me that either
- CVE-2024-30203 is just bogus, based on a misunderstanding by the CVEs
assigner of exactly what the vulnerabilities were
- CVE-2024-30203 is legitimate, and we have only fixed one possible way
in which Gnus treats inline MIME content as trusted.
I think it's the first one -- can you confirm?
Thanks.
--
Sean Whitton
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
next reply other threads:[~2024-04-08 7:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 7:05 Sean Whitton [this message]
2024-04-08 11:38 ` Is CVE-2024-30203 bogus? 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
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=874jccjpvy.fsf@melete.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=emacs-devel@gnu.org \
--cc=emacs@packages.debian.org \
--cc=oss-security@lists.openwall.com \
--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 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.