Bug 722694 - (CVE-2011-4099) CVE-2011-4099 capsh: does not chdir after chroot
CVE-2011-4099 capsh: does not chdir after chroot
Status: CLOSED ERRATA
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
Unspecified Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
impact=low,public=20110716,reported=2...
: Security
Depends On:
Blocks: 734217
  Show dependency treegraph
 
Reported: 2011-07-16 12:51 EDT by Steve Grubb
Modified: 2015-08-19 05:11 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2011-12-07 04:09:41 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)
Patch fixing bug (1.06 KB, patch)
2011-07-16 12:59 EDT, Steve Grubb
no flags Details | Diff

  None (edit)
Description Steve Grubb 2011-07-16 12:51:54 EDT
Description of problem:
The capsh program has a --chroot commandline option. Inspecting the code shows that it does not do a chdir("/") after calling chroot. This means that '.' is outside the chroot.

Additional info:
http://cwe.mitre.org/data/definitions/243.html
Comment 3 Steve Grubb 2011-07-16 12:59:43 EDT
Created attachment 513490 [details]
Patch fixing bug

The attached patch will be sent upstream.
Comment 4 Steve Grubb 2011-07-26 12:43:05 EDT
Upstream said they included the fix in 2.22. Its now public:

http://www.kernel.org/pub/linux/libs/security/linux-privs/libcap2/libcap-2.22.tar.gz

So, I would say we should push fixes out in Fedora at least.
Comment 12 Huzaifa S. Sidhpurwala 2011-11-18 01:04:59 EST
This issue does not affect the version of libcap as shipped with Red Hat Enterprise Linux 4 and 5.
Comment 13 errata-xmlrpc 2011-12-06 12:12:51 EST
This issue has been addressed in following products:

  Red Hat Enterprise Linux 6

Via RHSA-2011:1694 https://rhn.redhat.com/errata/RHSA-2011-1694.html

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