From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/jasper: Apply fix for CVE-2018-19541
Date: Fri, 06 Dec 2019 09:21:44 +0100 [thread overview]
Message-ID: <8736dxq2xz.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20191202115934.24216-1-jubalh@iodoru.org> (Michael Vetter's message of "Mon, 2 Dec 2019 12:59:32 +0100")
>>>>> "Michael" == Michael Vetter <jubalh@iodoru.org> writes:
> Add 0001-verify-data-range-CVE-2018-19541.patch:
> We need to verify the data is in the expected range. Otherwise we get
> problems later.
> Patch was proposed upstream[1] but upstream is very inactive. Linux
> distributions use the same fix to patch their packages.
> 1: https://github.com/mdadams/jasper/pull/211
> Signed-off-by: Michael Vetter <jubalh@iodoru.org>
Committed to 2019.02.x and 2019.08.x, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-12-06 8:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-02 11:59 [Buildroot] [PATCH 1/3] package/jasper: Apply fix for CVE-2018-19541 Michael Vetter
2019-12-02 11:59 ` [Buildroot] [PATCH 2/3] package/jasper: Apply fix for CVE-2018-19542 Michael Vetter
2019-12-02 12:42 ` Peter Korsgaard
2019-12-06 8:21 ` Peter Korsgaard
2019-12-02 11:59 ` [Buildroot] [PATCH 3/3] package/jasper: Apply fix for CVE-2018-19540 Michael Vetter
2019-12-02 12:43 ` Peter Korsgaard
2019-12-06 8:21 ` Peter Korsgaard
2019-12-02 12:42 ` [Buildroot] [PATCH 1/3] package/jasper: Apply fix for CVE-2018-19541 Peter Korsgaard
2019-12-06 8:21 ` Peter Korsgaard [this message]
2019-12-06 8:58 ` Peter Korsgaard
-- strict thread matches above, loose matches on Subject: below --
2019-12-02 9:51 Michael Vetter
2019-12-02 11:40 ` Peter Korsgaard
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=8736dxq2xz.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.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.
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.