From: Thomas Deutschmann <whissi@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Subject: [gentoo-announce] [ GLSA 201702-03 ] Firejail: Privilege escalation
Date: Thu, 9 Feb 2017 16:38:52 +0100 [thread overview]
Message-ID: <73b433c4-3067-0bcc-b4e4-0914651a3a36@gentoo.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 3146 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 201702-03
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
https://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: High
Title: Firejail: Privilege escalation
Date: February 09, 2017
Bugs: #607382
ID: 201702-03
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
Firejail is vulnerable to the escalation of privileges due to an
incomplete fix for CVE-2017-5180.
Background
==========
A SUID program that reduces the risk of security breaches by
restricting the running environment of untrusted applications using
Linux namespaces and seccomp-bpf.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 sys-apps/firejail < 0.9.44.8 >= 0.9.44.8
2 sys-apps/firejail-lts < 0.9.38.10 >= 0.9.38.10
-------------------------------------------------------------------
2 affected packages
Description
===========
The unaffected packages listed in GLSA 201612-48 had an incomplete fix
as reported by Sebastian Krahmer of SuSE. This has been properly
patched in the latest releases.
Impact
======
An attacker could possibly bypass sandbox protection, cause a Denial of
Service condition, or escalate privileges.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All Firejail users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=sys-apps/firejail-0.9.44.8"
All Firejail-lts users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot -v ">=sys-apps/firejail-lts-0.9.38.10"
References
==========
[ 1 ] CVE-2017-5940
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-5940
[ 2 ] Firejail Release Notes
https://firejail.wordpress.com/download-2/release-notes/
[ 3 ] GLSA 201612-48
https://security.gentoo.org/glsa/201612-48
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
https://security.gentoo.org/glsa/201702-03
Concerns?
=========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users' machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
https://bugs.gentoo.org.
License
=======
Copyright 2017 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
http://creativecommons.org/licenses/by-sa/2.5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 951 bytes --]
reply other threads:[~2017-02-09 15:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=73b433c4-3067-0bcc-b4e4-0914651a3a36@gentoo.org \
--to=whissi@gentoo.org \
--cc=gentoo-announce@lists.gentoo.org \
/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