From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Bernd Kuhls <bernd.kuhls@t-online.de>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/ghostscript: security bump to version 9.56.1
Date: Fri, 22 Jul 2022 09:46:11 +0200 [thread overview]
Message-ID: <87r12dvbcs.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20220629201756.571047-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Wed, 29 Jun 2022 22:17:56 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> Fix CVE-2022-2085: A NULL pointer dereference vulnerability was found in
> Ghostscript, which occurs when it tries to render a large number of bits
> in memory. When allocating a buffer device, it relies on an
> init_device_procs defined for the device that uses it as a prototype
> that depends upon the number of bits per pixel. For bpp > 64,
> mem_x_device is used and does not have an init_device_procs defined.
> This flaw allows an attacker to parse a large number of bits (more than
> 64 bits per pixel), which triggers a NULL pointer dereference flaw,
> causing an application to crash.
> Drop patch (already in version)
> https://www.ghostscript.com/doc/9.56.0/News.htm
> https://www.ghostscript.com/doc/9.56.1/News.htm
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2022.05.x and 2022.02.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-07-22 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 20:17 [Buildroot] [PATCH 1/1] package/ghostscript: security bump to version 9.56.1 Fabrice Fontaine
2022-07-02 13:54 ` Peter Korsgaard
2022-07-22 7:46 ` Peter Korsgaard [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r12dvbcs.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd.kuhls@t-online.de \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox