Bug 189436 - CVE-2006-1864 smbfs chroot issue
Summary: CVE-2006-1864 smbfs chroot issue
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel
Version: 3.0
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Peter Staubach
QA Contact: Brian Brock
Whiteboard: impact=moderate,source=secalert,repor...
Keywords: Security
Depends On:
TreeView+ depends on / blocked
Reported: 2006-04-19 22:51 UTC by Marcel Holtmann
Modified: 2007-11-30 22:07 UTC (History)
4 users (show)

Clone Of:
Last Closed: 2006-10-19 12:40:58 UTC

Attachments (Terms of Use)
Proposed patch (445 bytes, patch)
2006-05-09 20:22 UTC, Peter Staubach
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2006:0710 normal SHIPPED_LIVE Important: kernel security update 2006-10-19 12:39:53 UTC

Description Marcel Holtmann 2006-04-19 22:51:47 UTC
When doing a chroot inside of a smb-mounted filesystem (smbfs), it appears that
you can break out of it using "cd ..\\" (2 backslashes).

[root@server me]# pwd
[root@server me]# ls
bin  chroot  etc  lib
[root@server me]# chroot .
bash-2.05a# pwd
bash-2.05a# ls
bin  chroot  etc  lib
bash-2.05a# cd ..\\
bash-2.05a# pwd
bash-2.05a# ls
<list of files from parent>

Comment 2 Peter Staubach 2006-05-09 20:22:20 UTC
Created attachment 128811 [details]
Proposed patch

Comment 9 Ernie Petrides 2006-09-23 01:08:26 UTC
A fix for this problem has just been committed to the RHEL3 U9
patch pool this evening (in kernel version 2.4.21-47.1.EL).

Comment 10 Ernie Petrides 2006-10-13 21:51:43 UTC
A fix for this problem has also been committed to the RHEL3 E9
patch pool this evening (in kernel version 2.4.21-47.0.1.EL).

Comment 13 Red Hat Bugzilla 2006-10-19 12:40:58 UTC
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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