From: Sean Whitton <spwhitton@spwhitton.name>
To: Max Nikulin <manikulin@gmail.com>
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:12:37 +0800 [thread overview]
Message-ID: <8734rsdzzu.fsf@melete.silentflame.com> (raw)
In-Reply-To: <fb09b3ff-6187-46b3-b544-182e7dd76412@gmail.com> (Max Nikulin's message of "Wed, 10 Apr 2024 22:07:02 +0700")
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
Hello,
On Wed 10 Apr 2024 at 10:07pm +07, Max Nikulin wrote:
> On 10/04/2024 21:17, Salvatore Bonaccorso wrote:
>> On Wed, Apr 10, 2024 at 12:04:06PM +0000, Ihor Radchenko wrote:
>>>
>>> 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.
> [...]
>> If you think the CVE assignment is not valid, then you might ask for a
>> REJECT on https://cveform.mitre.org/ .
>
> Do 2 CVE numbers make sense to track fixes in Emacs and Org mode? Various
> versions of Org mode may be loaded to different versions of Emacs and both
> parties must have fixes to avoid the issue.
My understanding is that one CVE for the same vulnerability in multiple
code bases is normal.
--
Sean Whitton
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]
next prev parent reply other threads:[~2024-04-11 9:12 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 [this message]
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
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=8734rsdzzu.fsf@melete.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=emacs-devel@gnu.org \
--cc=emacs@packages.debian.org \
--cc=manikulin@gmail.com \
--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 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).