Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.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/clamav: security bump to version 0.103.5
Date: Wed, 26 Jan 2022 23:06:33 +0100	[thread overview]
Message-ID: <20220126230633.4a76c296@windsurf> (raw)
In-Reply-To: <20220124221047.2597699-1-fontaine.fabrice@gmail.com>

On Mon, 24 Jan 2022 23:10:47 +0100
Fabrice Fontaine <fontaine.fabrice@gmail.com> wrote:

> ClamAV 0.103.5 is a critical patch release with the following fix:
> 
>  - CVE-2022-20698: Fix for invalid pointer read that may cause a crash.
>    Affects 0.104.1, 0.103.4 and prior when ClamAV is compiled with
>    libjson-c and the CL_SCAN_GENERAL_COLLECT_METADATA scan option (the
>    clamscan --gen-json option) is enabled.
> 
> https://github.com/Cisco-Talos/clamav/blob/clamav-0.103.5/NEWS.md
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
> ---
>  package/clamav/clamav.hash | 2 +-
>  package/clamav/clamav.mk   | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Applied to master, thanks.

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2022-01-26 22:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-24 22:10 [Buildroot] [PATCH 1/1] package/clamav: security bump to version 0.103.5 Fabrice Fontaine
2022-01-26 22:06 ` Thomas Petazzoni [this message]
2022-01-28 21:12 ` 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=20220126230633.4a76c296@windsurf \
    --to=thomas.petazzoni@bootlin.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