All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/opencv3: security bump to version 3.4.9
Date: Sun, 12 Jan 2020 11:55:40 +0100	[thread overview]
Message-ID: <87o8v9c5ar.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200111160253.1449739-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Sat, 11 Jan 2020 17:02:53 +0100")

>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:

 > - Fix CVE-2019-14491: An issue was discovered in OpenCV before 3.4.7
 >   and 4.x before 4.1.1. There is an out of bounds read in the function
 >   cv::predictOrdered<cv::HaarEvaluator> in
 >   modules/objdetect/src/cascadedetect.hpp, which leads to denial of service.
 > - Fix CVE-2019-14492: An issue was discovered in OpenCV before 3.4.7
 >   and 4.x before 4.1.1. There is an out of bounds read/write in the
 >   function HaarEvaluator::OptFeature::calc in
 >   modules/objdetect/src/cascadedetect.hpp, which leads to denial of service.
 > - atomic workaround is not needed since version 3.4.8 and
 >   https://github.com/opencv/opencv/commit/464972855e25f71667009b8fe88092d11aab0297
 > - Update hash of license file (Xperience.AI added:
 >   https://github.com/opencv/opencv/commit/766465ce9483c20d54bfce422d285c077f6502bd)

 > Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Committed to 2019.02.x and 2019.11.x, thanks.

-- 
Bye, Peter Korsgaard

      parent reply	other threads:[~2020-01-12 10:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-11 16:02 [Buildroot] [PATCH 1/1] package/opencv3: security bump to version 3.4.9 Fabrice Fontaine
2020-01-11 21:39 ` Peter Korsgaard
2020-01-12 10:55 ` 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=87o8v9c5ar.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.