From: Salvatore Bonaccorso <carnil-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: oss-security-ZwoEplunGu1jrUoiu81ncdBPR1lH4CV8@public.gmane.org
Cc: Sean Whitton <spwhitton-PEZ64Ft4C9UnzZ6mRAm98g@public.gmane.org>,
emacs-R+A61+qa7K2F9N/2sQ04j0B+6BGkLq7r@public.gmane.org,
emacs-devel-mXXj517/zsQ@public.gmane.org
Subject: Re: Re: Is CVE-2024-30203 bogus? (Emacs)
Date: Wed, 10 Apr 2024 16:17:15 +0200 [thread overview]
Message-ID: <Zhafa3wcZONJX-_k@eldamar.lan> (raw)
In-Reply-To: <87o7ahe85l.fsf@localhost>
Hi,
On Wed, Apr 10, 2024 at 12:04:06PM +0000, Ihor Radchenko wrote:
> Sean Whitton <spwhitton-PEZ64Ft4C9UnzZ6mRAm98g@public.gmane.org> writes:
>
> > Hmm, thank you, but let me ask a follow-up question: do you agree with
> > me that there is only one security flaw covered by these two CVEs, and
> > CVE-2024-30203 is the superfluous one?
>
> Yes, CVE-2024-30203 title is superfluous.
> And CVE-2024-30204 title is not accurate - it only applies to
> certain attachments with specific (text/x-org) mime type.
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.
associated with:
https://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-29&id=937b9042ad7426acdcca33e3d931d8f495bdd804
If you think the CVE assignment is not valid, then you might ask for a
REJECT on https://cveform.mitre.org/ .
Regards,
Salvatore
next prev parent reply other threads:[~2024-04-10 14:17 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 [this message]
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=Zhafa3wcZONJX-_k@eldamar.lan \
--to=carnil-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=emacs-R+A61+qa7K2F9N/2sQ04j0B+6BGkLq7r@public.gmane.org \
--cc=emacs-devel-mXXj517/zsQ@public.gmane.org \
--cc=oss-security-ZwoEplunGu1jrUoiu81ncdBPR1lH4CV8@public.gmane.org \
--cc=spwhitton-PEZ64Ft4C9UnzZ6mRAm98g@public.gmane.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.
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.