From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/exiv2: annotate CVE-2019-13504
Date: Sat, 29 Feb 2020 23:21:54 +0100 [thread overview]
Message-ID: <20200229222154.GX8743@scaer> (raw)
In-Reply-To: <20200229213204.3703303-1-fontaine.fabrice@gmail.com>
Fabrice, All,
On 2020-02-29 22:32 +0100, Fabrice Fontaine spake thusly:
> CVE-2019-13504 is misclassified (by our CVE tracker) as affecting
> version 0.27.2, while in fact both commits that fixed this issue are
> already in this version.
>
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
I've applied patches 2 and 3, as I could follow the commit to upstream
you provided in the patches.
However, for patch 1, I have been able to track only one commit, but you
noted two. It would be nice if youc ould provide the sha1 for those two
commits.
Thanks! :-)
Regards,
Yann E. MORIN.
> ---
> package/exiv2/exiv2.mk | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/package/exiv2/exiv2.mk b/package/exiv2/exiv2.mk
> index 228b3a980e..09988f49b2 100644
> --- a/package/exiv2/exiv2.mk
> +++ b/package/exiv2/exiv2.mk
> @@ -10,6 +10,11 @@ EXIV2_INSTALL_STAGING = YES
> EXIV2_LICENSE = GPL-2.0+, BSD-3-Clause
> EXIV2_LICENSE_FILES = COPYING COPYING-CMAKE-SCRIPTS
>
> +# CVE-2019-13504 is misclassified (by our CVE tracker) as affecting version
> +# 0.27.2, while in fact both commits that fixed this issue are already in this
> +# version.
> +EXIV2_IGNORE_CVES += CVE-2019-13504
> +
> EXIV2_CONF_OPTS += -DEXIV2_ENABLE_BUILD_SAMPLES=OFF
>
> # The following CMake variable disables a TRY_RUN call in the -pthread
> --
> 2.25.0
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2020-02-29 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-29 21:32 [Buildroot] [PATCH 1/3] package/exiv2: annotate CVE-2019-13504 Fabrice Fontaine
2020-02-29 21:32 ` [Buildroot] [PATCH 2/3] package/exiv2: fix CVE-2019-17402 Fabrice Fontaine
2020-03-14 17:58 ` Peter Korsgaard
2020-02-29 21:32 ` [Buildroot] [PATCH 3/3] package/exiv2: fix CVE-2019-20421 Fabrice Fontaine
2020-03-14 17:58 ` Peter Korsgaard
2020-02-29 22:21 ` Yann E. MORIN [this message]
2020-02-29 22:28 ` [Buildroot] [PATCH 1/3] package/exiv2: annotate CVE-2019-13504 Fabrice Fontaine
2020-03-01 7:29 ` Yann E. MORIN
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=20200229222154.GX8743@scaer \
--to=yann.morin.1998@free.fr \
--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.