Bug 921448 - (CVE-2013-1858) CVE-2013-1858 kernel: CLONE_NEWUSER | CLONE_FS chroot exploit
CVE-2013-1858 kernel: CLONE_NEWUSER | CLONE_FS chroot exploit
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
high Severity high
: ---
: ---
Assigned To: Red Hat Product Security
impact=important,public=20130313,repo...
: Security
Depends On:
Blocks: 921413
  Show dependency treegraph
 
Reported: 2013-03-14 04:50 EDT by Prasad J Pandit
Modified: 2015-07-31 03:00 EDT (History)
28 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2013-05-10 07:50:04 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Prasad J Pandit 2013-03-14 04:50:15 EDT
Linux kernels which support unprivileged user namespaces (CLONE_NEWUSER) and at the same time allow sharing file system information (CLONE_FS) between parent process and its newly clone(2)d child process in the new user namespace, are vulnerable to a privilege escalation flaw as presented by Sebastian Krahmer
in his chroot exploit [1].

  [1] http://stealth.openwall.net/xSports/clown-newuser.c

An unprivileged local user could use this flaw to gain root privileges on a system.

Upstream fix:
-------------
 -> https://git.kernel.org/linus/e66eded8309ebf679d3d3c1f5820d1f2ca332c71

Reference:
----------
 -> http://www.openwall.com/lists/oss-security/2013/03/13/8
Comment 1 Prasad J Pandit 2013-03-14 04:56:09 EDT
Statement:

This issue did not affect the versions of the Linux kernel as shipped with Red Hat Enterprise Linux 5, 6, and Red Hat Enterprise MRG 2.

This issue did not affect the versions of the Linux kernel as shipped with Fedora 17 and 18 as they were not built with CONFIG_USER_NS configuration option.

Note You need to log in before you can comment on or make changes to this bug.