Skip to contentSkip to conversation

package/lxc: security bump to version 3.2.1

PATCH New Fabrice Fontaine 5 participants 7 messages Aug 16, 2019 – Oct 5, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 package/lxc: security bump to version 3.2.1

- lxc switched from gnutls to openssl since version 3.2.0 and
https://github.com/lxc/lxc/commit/fa2bb6ba532c5e7f92df8cbae50a68af519f9997
- lxc needs a glibc or musl toolchain since version 3.2.0 and
https://github.com/lxc/lxc/commit/6400238d08cdf1ca20d49bafb85f4e224348bf9d
- This version includes a security fix (named CVE-2019-5736 on runC):
https://github.com/lxc/lxc/commit/6400238d08cdf1ca20d49bafb85f4e224348bf9d

---
 package/lxc/Config.in |  5 +++--
 package/lxc/lxc.hash  |  2 +-
 package/lxc/lxc.mk    | 16 ++++++++--------
 3 files changed, 12 insertions(+), 11 deletions(-)
package/lxc/Config.in +3 -2
index d8d8f50c8e..0b3c1b923e 100644
@@ -6,6 +6,7 @@ config BR2_PACKAGE_LXC
 	depends on !BR2_STATIC_LIBS
 	depends on BR2_TOOLCHAIN_GCC_AT_LEAST_4_7 # C++11
 	depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_0 # setns() system call
+	depends on !BR2_TOOLCHAIN_USES_UCLIBC # no fexecve
 	help
 	  Linux Containers (LXC), provides the ability to group and
 	  isolate of a set of processes in a jail by virtualizing and
@@ -14,9 +15,9 @@ config BR2_PACKAGE_LXC
 
 	  https://linuxcontainers.org/
 
-comment "lxc needs a toolchain w/ threads, headers >= 3.0, dynamic library, gcc >= 4.7"
+comment "lxc needs a glibc or musl toolchain w/ threads, headers >= 3.0, dynamic library, gcc >= 4.7"
 	depends on BR2_USE_MMU
 	depends on !BR2_TOOLCHAIN_HAS_THREADS \
 		|| !BR2_TOOLCHAIN_GCC_AT_LEAST_4_7 \
 		|| !BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_0 \
-		|| BR2_STATIC_LIBS
+		|| BR2_STATIC_LIBS || BR2_TOOLCHAIN_USES_UCLIBC
package/lxc/lxc.hash +1 -1
index aad38ca57a..d5ea799776 100644
@@ -1,3 +1,3 @@
 # Locally calculated
-sha256	4d8772c25baeaea2c37a954902b88c05d1454c91c887cb6a0997258cfac3fdc5	lxc-3.1.0.tar.gz
+sha256	5f903986a4b17d607eea28c0aa56bf1e76e8707747b1aa07d31680338b1cc3d4	lxc-3.2.1.tar.gz
 sha256	dc626520dcd53a22f727af3ee42c770e56c97a64fe3adb063799d8ab032fe551	COPYING
package/lxc/lxc.mk +8 -8
index a059fd578e..81adeef5ee 100644
@@ -4,7 +4,7 @@
 #
 ################################################################################
 
-LXC_VERSION = 3.1.0
+LXC_VERSION = 3.2.1
 LXC_SITE = https://linuxcontainers.org/downloads/lxc
 LXC_LICENSE = LGPL-2.1+
 LXC_LICENSE_FILES = COPYING
@@ -19,13 +19,6 @@ ifeq ($(BR2_PACKAGE_BASH_COMPLETION),y)
 LXC_DEPENDENCIES += bash-completion
 endif
 
-ifeq ($(BR2_PACKAGE_GNUTLS),y)
-LXC_CONF_OPTS += --enable-gnutls
-LXC_DEPENDENCIES += gnutls
-else
-LXC_CONF_OPTS += --disable-gnutls
-endif
-
 ifeq ($(BR2_PACKAGE_LIBCAP),y)
 LXC_CONF_OPTS += --enable-capabilities
 LXC_DEPENDENCIES += libcap
@@ -47,4 +40,11 @@ else
 LXC_CONF_OPTS += --disable-selinux
 endif
 
+ifeq ($(BR2_PACKAGE_OPENSSL),y)
+LXC_CONF_OPTS += --enable-openssl
+LXC_DEPENDENCIES += openssl
+else
+LXC_CONF_OPTS += --disable-openssl
+endif
+
 $(eval $(autotools-package))
Signature · 1 line
2.20.1
#1 lore raw

PATCH 1/1 package/lxc: security bump to version 3.2.1

Quoted 8 lines · On Fri, 16 Aug 2019 19:03:15 +0200 Fabrice Fontaine…

- lxc switched from gnutls to openssl since version 3.2.0 and
https://github.com/lxc/lxc/commit/fa2bb6ba532c5e7f92df8cbae50a68af519f9997
- lxc needs a glibc or musl toolchain since version 3.2.0 and
https://github.com/lxc/lxc/commit/6400238d08cdf1ca20d49bafb85f4e224348bf9d
- This version includes a security fix (named CVE-2019-5736 on runC):
https://github.com/lxc/lxc/commit/6400238d08cdf1ca20d49bafb85f4e224348bf9d

We normally apply security bumps to master. But this one seems like a quite major bump, and it also disables the package for uClibc.

Does it make sense to backport just the security fix in master ?

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
#2 lore raw

PATCH 1/1 package/lxc: security bump to version 3.2.1

Hello Thomas,

Le sam. 17 ao?t 2019 ? 15:41, Thomas Petazzoni
<[email protected]> a ?crit :

Quoted 11 lines
Quoted 7 lines · On Fri, 16 Aug 2019 19:03:15 +0200 Fabrice Fontaine…

- lxc switched from gnutls to openssl since version 3.2.0 and
https://github.com/lxc/lxc/commit/fa2bb6ba532c5e7f92df8cbae50a68af519f9997
- lxc needs a glibc or musl toolchain since version 3.2.0 and
https://github.com/lxc/lxc/commit/6400238d08cdf1ca20d49bafb85f4e224348bf9d
- This version includes a security fix (named CVE-2019-5736 on runC):
https://github.com/lxc/lxc/commit/6400238d08cdf1ca20d49bafb85f4e224348bf9d

Quoted 4 lines
Quoted 1 line

We normally apply security bumps to master. But this one seems like a quite major bump, and it also disables the package for uClibc.

Yes I know that's why I marked it for next.

Quoted 2 lines

Does it make sense to backport just the security fix in master ?

I could but this fix will add the glibc or musl toolchain dependency.

Quoted 6 lines

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

Best Regards,

Fabrice

#3 lore raw

PATCH 1/1 package/lxc: security bump to version 3.2.1

Hello,

+Peter in Cc.

Quoted 15 lines · On Sat, 17 Aug 2019 21:36:27 +0200 Fabrice Fontaine…

Hello Thomas,

Le sam. 17 ao?t 2019 ? 15:41, Thomas Petazzoni
<[email protected]> a ?crit :

Quoted 11 lines
Quoted 7 lines · On Fri, 16 Aug 2019 19:03:15 +0200 Fabrice Fontaine…

- lxc switched from gnutls to openssl since version 3.2.0 and
https://github.com/lxc/lxc/commit/fa2bb6ba532c5e7f92df8cbae50a68af519f9997
- lxc needs a glibc or musl toolchain since version 3.2.0 and
https://github.com/lxc/lxc/commit/6400238d08cdf1ca20d49bafb85f4e224348bf9d
- This version includes a security fix (named CVE-2019-5736 on runC):
https://github.com/lxc/lxc/commit/6400238d08cdf1ca20d49bafb85f4e224348bf9d

Quoted 8 lines
Quoted 4 lines
Quoted 1 line

We normally apply security bumps to master. But this one seems like a quite major bump, and it also disables the package for uClibc.

Yes I know that's why I marked it for next.

Quoted 2 lines

Does it make sense to backport just the security fix in master ?

I could but this fix will add the glibc or musl toolchain dependency.

OK, so let's bring Peter Korsgaard in Cc. Since he maintains the stable/LTS branches, it is important to get his call on this issue.

Thanks,

Thomas

Signature · 3 lines
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
#4 lore raw

PATCH 1/1 package/lxc: security bump to version 3.2.1

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Thomas" == Thomas Petazzoni <[email protected]> writes:

Hi,

Quoted 5 lines
Quoted 2 lines
Quoted 1 line

Does it make sense to backport just the security fix in master ?

I could but this fix will add the glibc or musl toolchain dependency.

OK, so let's bring Peter Korsgaard in Cc. Since he maintains the stable/LTS branches, it is important to get his call on this issue.

Well, is is "complicated" ;) CVE-2019-5736 is the same issue we fixed for runc back in February (where the fix had some fallout).

But do notice:

- Issue only applies to privileged containers, which is explicitly marked as unsafe by upstream - E.G. on their website:

They're not safe at all and should only be used in environments where unprivileged containers aren't available and where you would trust your container's user with root access to the host.

https://linuxcontainers.org/lxc/security/#LXC

- The current lxc version in 2019.02.x / 2019.05.x / 2019.08 is 3.1.0, which is a development version of late 2018.

- A fix is available for the current LTS version (3.0.x, supported until 2023) and current development version (3.2.1)

So our options are basically:

- Apply the patch to master and 2019.02.x / 2019.05.x

- Revert master/2019.05.x/2019.02.x to the LTS series, 3.0.4

- Cherry pick the fix to 3.1.0 for master/2019.05.x/2019.02.x

- Ignore the issue and only apply the patch to next

I would say option 4 (ignore) or 2 (revert) sounds like the most sensible options to me.

What do others think?

Signature · 1 line
Bye, Peter Korsgaard
#5 lore raw

PATCH 1/1 package/lxc: security bump to version 3.2.1

Quoted 39 lines · Peter Korsgaard
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Thomas" == Thomas Petazzoni <[email protected]> writes:

Hi,

Quoted 5 lines
Quoted 2 lines
Quoted 1 line

Does it make sense to backport just the security fix in master ?

I could but this fix will add the glibc or musl toolchain dependency.

OK, so let's bring Peter Korsgaard in Cc. Since he maintains the stable/LTS branches, it is important to get his call on this issue.

Well, is is "complicated" ;) CVE-2019-5736 is the same issue we fixed for runc back in February (where the fix had some fallout).

But do notice:

- Issue only applies to privileged containers, which is explicitly marked as unsafe by upstream - E.G. on their website:

They're not safe at all and should only be used in environments where unprivileged containers aren't available and where you would trust your container's user with root access to the host.

https://linuxcontainers.org/lxc/security/#LXC

- The current lxc version in 2019.02.x / 2019.05.x / 2019.08 is 3.1.0, which is a development version of late 2018.

- A fix is available for the current LTS version (3.0.x, supported until 2023) and current development version (3.2.1)

So our options are basically:

- Apply the patch to master and 2019.02.x / 2019.05.x

- Revert master/2019.05.x/2019.02.x to the LTS series, 3.0.4

- Cherry pick the fix to 3.1.0 for master/2019.05.x/2019.02.x

Quoted 7 lines

- Ignore the issue and only apply the patch to next

I would say option 4 (ignore) or 2 (revert) sounds like the most sensible options to me.

What do others think?

I tend to lean towards option 2, but option 4 is fine as well of course.

Note that I scheduled a discussion about this type of problem (our LTS branch
ends up with a non-LTS version) for the developer meeting.

Regards,
Arnout

#6 lore raw

PATCH 1/1 package/lxc: security bump to version 3.2.1

In reply to Fabrice Fontaine

Am Fri, 16 Aug 2019 19:03:15 +0200 schrieb Fabrice Fontaine:

Quoted 2 lines

Signed-off-by: Fabrice Fontaine
<[email protected]>

[build-tested using this defconfig:
BR2_x86_64=y
BR2_x86_atom=y
BR2_TOOLCHAIN_EXTERNAL=y
BR2_TOOLCHAIN_EXTERNAL_DOWNLOAD=y BR2_TOOLCHAIN_EXTERNAL_URL="http://autobuild.buildroot.org/toolchains/ tarballs/br-x86-64-musl-2019.05.1.tar.bz2" BR2_TOOLCHAIN_EXTERNAL_GCC_7=y BR2_TOOLCHAIN_EXTERNAL_HEADERS_5_1=y BR2_TOOLCHAIN_EXTERNAL_CUSTOM_MUSL=y BR2_TOOLCHAIN_EXTERNAL_CXX=y
BR2_PACKAGE_OPENSSL=y
BR2_PACKAGE_LIBCAP=y
BR2_PACKAGE_LIBSECCOMP=y
BR2_PACKAGE_LXC=y]