From: Peter Korsgaard <peter@korsgaard.com>
To: Titouan Christophe via buildroot <buildroot@buildroot.org>
Cc: Titouan Christophe <titouan.christophe@mind.be>
Subject: Re: [Buildroot] [PATCH] package/imagemagick: security bump to v7.1.2-3
Date: Wed, 03 Sep 2025 18:15:50 +0200 [thread overview]
Message-ID: <87tt1jms09.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20250903124306.6936-1-titouan.christophe@mind.be> (Titouan Christophe via buildroot's message of "Wed, 3 Sep 2025 14:43:06 +0200")
>>>>> "Titouan" == Titouan Christophe via buildroot <buildroot@buildroot.org> writes:
> This fixes the following vulnerabilities:
> - CVE-2023-5341:
> A heap use-after-free flaw was found in coders/bmp.c in ImageMagick.
> https://www.cve.org/CVERecord?id=CVE-2023-5341
> - CVE-2025-55004:
> ImageMagick is free and open-source software used for editing and
> manipulating digital images. Prior to version 7.1.2-1, ImageMagick is
> vulnerable to heap-buffer overflow read around the handling of images
> with separate alpha channels when performing image magnification in
> ReadOneMNGIMage. This can likely be used to leak subsequent memory
> contents into the output image. This issue has been patched in version
> 7.1.2-1.
> https://www.cve.org/CVERecord?id=CVE-2025-55004
> - CVE-2025-55005:
> ImageMagick is free and open-source software used for editing and
> manipulating digital images. Prior to version 7.1.2-1, when preparing
> to transform from Log to sRGB colorspaces, the logmap construction
> fails to handle cases where the reference-black or reference-white
> value is larger than 1024. This leads to corrupting memory beyond the
> end of the allocated logmap buffer. This issue has been patched in
> version 7.1.2-1.
> https://www.cve.org/CVERecord?id=CVE-2025-55005
> - CVE-2025-55160:
> ImageMagick is free and open-source software used for editing and
> manipulating digital images. Prior to versions 6.9.13-27 and 7.1.2-1,
> there is undefined behavior (function-type-mismatch) in splay tree
> cloning callback. This results in a deterministic abort under UBSan
> (DoS in sanitizer builds), with no crash in a non-sanitized build.
> This issue has been patched in versions 6.9.13-27 and 7.1.2-1.
> https://www.cve.org/CVERecord?id=CVE-2025-55160
> Signed-off-by: Titouan Christophe <titouan.christophe@mind.be>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-09-03 16:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-03 12:43 [Buildroot] [PATCH] package/imagemagick: security bump to v7.1.2-3 Titouan Christophe via buildroot
2025-09-03 16:15 ` Peter Korsgaard [this message]
2025-09-03 17:24 ` Thomas Perale via buildroot
2025-09-11 19:23 ` Thomas Perale via buildroot
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=87tt1jms09.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=titouan.christophe@mind.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.
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.