From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package/proftpd: security bump to version 1.3.6c
Date: Thu, 27 Feb 2020 18:26:36 +0100 [thread overview]
Message-ID: <20200227182636.6dffccc8@windsurf> (raw)
In-Reply-To: <20200227135457.13710-1-peter@korsgaard.com>
On Thu, 27 Feb 2020 14:54:56 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:
> Fixes the following security issues:
>
> - CVE-2020-9273: In ProFTPD 1.3.7, it is possible to corrupt the memory pool
> by interrupting the data transfer channel. This triggers a use-after-free
> in alloc_pool in pool.c, and possible remote code execution.
>
> And additionally, fixes a number of other issues. For details, see the
> release notes:
>
> https://github.com/proftpd/proftpd/blob/1.3.6/RELEASE_NOTES
>
> This also bumps the bundled libcap, so
> 0001-fix-kernel-header-capability-version.patch can be dropped.
>
> While we are at it, adjust the white space in the .hash function to match
> the new agreements.
>
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> ---
> .../0001-fix-kernel-header-capability-version.patch | 12 ------------
> package/proftpd/proftpd.hash | 4 ++--
> package/proftpd/proftpd.mk | 2 +-
> 3 files changed, 3 insertions(+), 15 deletions(-)
> delete mode 100644 package/proftpd/0001-fix-kernel-header-capability-version.patch
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-02-27 17:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 13:54 [Buildroot] [PATCH] package/proftpd: security bump to version 1.3.6c Peter Korsgaard
2020-02-27 17:26 ` Thomas Petazzoni [this message]
2020-03-14 16:47 ` 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=20200227182636.6dffccc8@windsurf \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox