From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Bernd Kuhls <bernd@kuhls.net>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/ghostscript: security bump to version 10.02.0
Date: Mon, 25 Sep 2023 07:40:20 +0200 [thread overview]
Message-ID: <87il7yerp7.fsf@48ers.dk> (raw)
In-Reply-To: <20230920170711.3901-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Wed, 20 Sep 2023 19:07:11 +0200")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> - Fix CVE-2023-36664: Artifex Ghostscript through 10.01.2 mishandles
> permission validation for pipe devices (with the %pipe% prefix or the |
> pipe character prefix).
> - Fix CVE-2023-38559: A buffer overflow flaw was found in
> base/gdevdevn.c:1973 in devn_pcx_write_rle() in ghostscript. This
> issue may allow a local attacker to cause a denial of service via
> outputting a crafted PDF file for a DEVN device with gs.
> - Fix CVE-2023-38560: An integer overflow flaw was found in
> pcl/pl/plfont.c:418 in pl_glyph_name in ghostscript. This issue may
> allow a local attacker to cause a denial of service via transforming a
> crafted PCL file to PDF format.
> https://ghostscript.readthedocs.io/en/gs10.02.0/News.html
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed to 2023.02.x, 2023.05.x and 2023.08.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-09-25 5:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 17:07 [Buildroot] [PATCH 1/1] package/ghostscript: security bump to version 10.02.0 Fabrice Fontaine
2023-09-20 17:33 ` Yann E. MORIN
2023-09-25 5:40 ` 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=87il7yerp7.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd@kuhls.net \
--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