All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/syslog-ng: Ignore CVE-2008-5110
Date: Thu, 22 Oct 2020 15:43:28 +0200	[thread overview]
Message-ID: <20201022154328.26b50fad@windsurf.home> (raw)
In-Reply-To: <20201021074424.13589-1-judge.packham@gmail.com>

Hello Chris,

On Wed, 21 Oct 2020 20:44:24 +1300
Chris Packham <judge.packham@gmail.com> wrote:

> This as fixed in syslog-ng 2.0.10 but the NVD database hasn't been
> updated.
> 
> Signed-off-by: Chris Packham <judge.packham@gmail.com>
> ---
>  package/syslog-ng/syslog-ng.mk | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/package/syslog-ng/syslog-ng.mk b/package/syslog-ng/syslog-ng.mk
> index 7c2368efba..8587da746a 100644
> --- a/package/syslog-ng/syslog-ng.mk
> +++ b/package/syslog-ng/syslog-ng.mk
> @@ -17,6 +17,10 @@ SYSLOG_NG_AUTORECONF = YES
>  SYSLOG_NG_CONF_OPTS = --disable-manpages --localstatedir=/var/run \
>  	--disable-java --disable-java-modules --disable-mongodb
>  
> +# CVE-2008-5110 was fixed in syslog-ng 2.0.10 but the NVD database is not
> +# aware of the fix, ignore it
> +SYSLOG_NG_IGNORE_CVES += CVE-2008-5110

But as proposed over e-mail separately, the proper fix is to modify the
NVD database. Have you had the chance to report the issue to the NVD
database maintainers ?

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-10-22 13:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-21  7:44 [Buildroot] [PATCH] package/syslog-ng: Ignore CVE-2008-5110 Chris Packham
2020-10-22 13:43 ` Thomas Petazzoni [this message]
2020-11-02  6:54   ` Chris Packham
2020-11-11  7:22     ` Chris Packham
2020-11-14  4:17       ` Chris Packham

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=20201022154328.26b50fad@windsurf.home \
    --to=thomas.petazzoni@bootlin.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.