From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Maxime Devos <maximedevos@telenet.be>
Cc: 47259-done@debbugs.gnu.org
Subject: bug#47259: python-pillow-simd package vulnerable to at least CVE-2021-25293
Date: Wed, 23 Mar 2022 12:13:32 -0400 [thread overview]
Message-ID: <87mthgy7df.fsf@gmail.com> (raw)
In-Reply-To: <7318489400ae1f00a40463e55f9637fe41d8e35e.camel@telenet.be> (Maxime Devos's message of "Wed, 23 Mar 2022 13:39:25 +0100")
Hi,
Maxime Devos <maximedevos@telenet.be> writes:
> Maxim Cournoyer schreef op di 22-03-2022 om 22:57 [-0400]:
>> Léo Le Bouter <lle-bout@zaclys.net> writes:
>>
>> > Hello!
>> >
>> > pillow-simd is a fork of pillow (
>> > https://github.com/uploadcare/pillow-simd), it's currently still at
>> > version 7.x and it does not seem like it backports security patches
>> > from pillow.
>>
>> Thanks for the heads-up; our package is currently at 9.0.0, and I've
>> just updated it to 9.0.0.post1.
>
> Something went wrong
> <https://git.savannah.gnu.org/cgit/guix.git/commit/?id=4a828263791ebb8ed8f8104e015a8f467008fc76>:
> the version in the version field contains a "v" prefix which is dropped
> in Guix.
> Additionally, the package name is missing from the commit message,
> though that cannot be corrected retroactively.
Hum, apologies, it must have been late :-).
> WDYT of removing the "v", and changing the "commit" field to
>
> (commit (string-append "v" version))
>
I see that Nicholas has already fixed it; thank you!
Maxim
prev parent reply other threads:[~2022-03-23 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 10:37 bug#47259: python-pillow-simd package vulnerable to at least CVE-2021-25293 Léo Le Bouter via Bug reports for GNU Guix
2022-03-23 2:57 ` Maxim Cournoyer
2022-03-23 12:39 ` Maxime Devos
2022-03-23 16:13 ` Maxim Cournoyer [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mthgy7df.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=47259-done@debbugs.gnu.org \
--cc=maximedevos@telenet.be \
/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/guix.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).