Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/chrony: security bump to version 3.5.1
Date: Sun, 23 Aug 2020 15:31:42 +0200	[thread overview]
Message-ID: <20200823133142.GG8728@scaer> (raw)
In-Reply-To: <20200821205105.733-1-peter@korsgaard.com>

Peter, All,

On 2020-08-21 22:51 +0200, Peter Korsgaard spake thusly:
> Fixes the following security issues:
> 
> CVE-2020-14367: Insecure writing of pidfile
> -------------------------------------------
> 
> When chronyd is configured to save the pidfile in a directory where the
> chrony user has write permissions (e.g. /var/run/chrony - the default
> since chrony-3.4), an attacker that compromised the chrony user account
> could create a symbolic link at the location of the pidfile to make
> chronyd starting with root privileges follow the symlink and write its
> process ID to a file for which the chrony user doesn't have write
> permissions, causing a denial of service, or data loss.
> 
> This issue was reported by Matthias Gerstner of SUSE.
> 
> For further details, see the oss-security posting:
> https://www.openwall.com/lists/oss-security/2020/08/21/1
> 
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Security fix => applied to master, thanks.

Regards,
Yann E. MORIN.

> ---
>  package/chrony/chrony.hash | 7 +++----
>  package/chrony/chrony.mk   | 2 +-
>  2 files changed, 4 insertions(+), 5 deletions(-)
> 
> diff --git a/package/chrony/chrony.hash b/package/chrony/chrony.hash
> index c31c6893aa..57ce91ac80 100644
> --- a/package/chrony/chrony.hash
> +++ b/package/chrony/chrony.hash
> @@ -1,5 +1,4 @@
> -# From https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-announce/2019/05/msg00001.html
> -md5 5f66338bc940a9b51eede8f391e7bed3  chrony-3.5.tar.gz
> -sha1 79e9aeace143550300387a99f17bff04b45673f7  chrony-3.5.tar.gz
> +# From https://listengine.tuxfamily.org/chrony.tuxfamily.org/chrony-announce/2020/08/msg00000.html
> +sha256  1ba82f70db85d414cd7420c39858e3ceca4b9eb8b028cbe869512c3a14a2dca7  chrony-3.5.1.tar.gz
>  # Locally calculated
> -sha256 ab15fd526bd8dd18a9e77ebc139656bf4d33e97fc7238cd11bf60e2b9b8666c6  COPYING
> +sha256  ab15fd526bd8dd18a9e77ebc139656bf4d33e97fc7238cd11bf60e2b9b8666c6  COPYING
> diff --git a/package/chrony/chrony.mk b/package/chrony/chrony.mk
> index d7f5c05183..f8938a80f5 100644
> --- a/package/chrony/chrony.mk
> +++ b/package/chrony/chrony.mk
> @@ -4,7 +4,7 @@
>  #
>  ################################################################################
>  
> -CHRONY_VERSION = 3.5
> +CHRONY_VERSION = 3.5.1
>  CHRONY_SITE = http://download.tuxfamily.org/chrony
>  CHRONY_LICENSE = GPL-2.0
>  CHRONY_LICENSE_FILES = COPYING
> -- 
> 2.20.1
> 
> _______________________________________________
> 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.  |
'------------------------------^-------^------------------^--------------------'

  reply	other threads:[~2020-08-23 13:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-21 20:51 [Buildroot] [PATCH] package/chrony: security bump to version 3.5.1 Peter Korsgaard
2020-08-23 13:31 ` Yann E. MORIN [this message]
2020-08-28 17:03 ` 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=20200823133142.GG8728@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox