[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[SECURITY] [DSA 3317-1] lxc security update



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

- -------------------------------------------------------------------------
Debian Security Advisory DSA-3317-1                   security@debian.org
https://www.debian.org/security/                     Salvatore Bonaccorso
July 25, 2015                         https://www.debian.org/security/faq
- -------------------------------------------------------------------------

Package        : lxc
CVE ID         : CVE-2015-1331 CVE-2015-1334
Debian Bug     : 793298

Several vulnerabilities have been discovered in LXC, the Linux
Containers userspace tools. The Common Vulnerabilities and Exposures
project identifies the following problems:

CVE-2015-1331

    Roman Fiedler discovered a directory traversal flaw in LXC when
    creating lock files. A local attacker could exploit this flaw to
    create an arbitrary file as the root user.

CVE-2015-1334

    Roman Fiedler discovered that LXC incorrectly trusted the
    container's proc filesystem to set up AppArmor profile changes and
    SELinux domain transitions. A malicious container could create a
    fake proc filesystem and use this flaw to run programs inside the
    container that are not confined by AppArmor or SELinux.

For the stable distribution (jessie), these problems have been fixed in
version 1:1.0.6-6+deb8u1.

For the testing distribution (stretch), these problems have been fixed
in version 1:1.0.7-4.

For the unstable distribution (sid), these problems have been fixed in
version 1:1.0.7-4.

We recommend that you upgrade your lxc packages.

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/

Mailing list: debian-security-announce@lists.debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBCgAGBQJVs6LAAAoJEAVMuPMTQ89EP8kP/iJUCwyKpqnqhKjfBhvHSVKX
4QsAubBAVLwmqLnT5DT1BghXHpeQFdQsl6CTfDas2H6SbwV5pJeZFWyItLVA1shf
6ocFssYQtKjM8q85zEYIPc1xiwuQpHsS270xh/hR75XSTYbBjpZ+wbCKrZGjqhQU
QOBME9CIEeyhGfToaGxh4f1FDcxT/YStq49ISgqrJ+4qFeJiCMvBkOIHeXTwKkxs
sKgXx7fJ90PVqSRDWCFggLQENpkTmftS4IAGF22VCRP8dO1Bnwz0TZVl5TzXe+22
r+L3BWie1W6jclMXTzphu5DyYOwo2mSylUmEhOkG7E8JIO3wc0AdK6hXqE/lNSGe
eUx2DRVw3R4yFOKs+LDLAgntuBbMqRAR+lEeifNrr9i8RzxHnf27fm3qGDdKIohd
mTt18f6L/hYdN372D4IpF/unA1uPMYmtnz9VCTK6Y5ppooOaxCkh3mPUe3vVZapa
X/Gahw67/1z7TI8b0wt0Hx/fxdkoTmubMU28o/qeWWu5aheA7MU69+EqpXiU2xxl
xpNy/7oCpdFswowcSpQ8DdzQBO8alLnu6j7s3d5vn87f7QIyZ2PIB61PEB61JBpC
ssi7CQzdV9OrnUb+mAZ48V3YfT73duO2C8NI3fi3cVdWjFWyvC/QKHbKOOUYutiV
pMFQTIT+IdFpU/c0fowx
=mtWe
-----END PGP SIGNATURE-----


Reply to: