unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: Add Nagios.
Date: Sat, 31 Dec 2016 18:41:08 +0100	[thread overview]
Message-ID: <878tqw2dzf.fsf@gnu.org> (raw)
In-Reply-To: <20161230195216.GA9049@jasmine> (Leo Famulari's message of "Fri, 30 Dec 2016 14:52:16 -0500")

Leo Famulari <leo@famulari.name> skribis:

> On Wed, Nov 30, 2016 at 10:31:09PM +0000, Ludovic Court�s wrote:
>> civodul pushed a commit to branch master
>> in repository guix.
>> 
>> commit d30e578a0011b05d1e7d8b3ba7ee38588eba301c
>> Author: Ludovic Courtès <ludo@gnu.org>
>> Date:   Wed Nov 30 23:26:57 2016 +0100
>> 
>>     gnu: Add Nagios.
>>     
>>     * gnu/packages/monitoring.scm: New file.
>>     * gnu/local.mk (GNU_SYSTEM_MODULES): Add it.
>
>> +    (version "4.0.8")
>> +    ;; XXX: Newer versions such as 4.2.3 bundle a copy of AngularJS.
>
> This version of Nagios includes some severe security vulnerabilities:
>
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9566
> https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-9565
>
> They allow remote attackers to read and write arbitrary files (leading
> to remote code execution) or to escalate privilege to the superuser.
>
> What should we do?

We should upgrade, even if that means bundling AngularJS (there’s no
other way :-/).  I’ll look into it ASAP.

Thanks for the reminder!

Ludo’.

  reply	other threads:[~2016-12-31 17:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161130223109.19603.88396@vcs.savannah.gnu.org>
     [not found] ` <20161130223109.CCC082201C1@vcs.savannah.gnu.org>
2016-12-30 19:52   ` 01/01: gnu: Add Nagios Leo Famulari
2016-12-31 17:41     ` Ludovic Courtès [this message]
2016-12-31 19:05     ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878tqw2dzf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).