Hash: SHA1

             AUSCERT External Security Bulletin Redistribution

               devfs rules not applied by default for jails
                               30 April 2014


        AusCERT Security Bulletin Summary

Product:           devfs
Publisher:         FreeBSD
Operating System:  FreeBSD
                   UNIX variants (UNIX, Linux, OSX)
Impact/Access:     Root Compromise          -- Existing Account
                   Access Confidential Data -- Existing Account
Resolution:        Patch/Upgrade
CVE Names:         CVE-2014-3001  

Original Bulletin: 

Comment: This advisory references vulnerabilities in products which run on 
         platforms other than FreeBSD. It is recommended that administrators
         running devfs check for an updated version of the software for their
         operating system.

- --------------------------BEGIN INCLUDED TEXT--------------------

Hash: SHA512

FreeBSD-SA-14:07.devfs                                      Security Advisory
                                                          The FreeBSD Project

Topic:          devfs rules not applied by default for jails

Category:       core
Module:         etc_rc.d
Announced:      2014-04-30
Affects:        FreeBSD 10.0
Corrected:      2014-04-30 04:03:05 UTC (stable/10, 10.0-STABLE)
                2014-04-30 04:04:42 UTC (releng/10.0, 10.0-RELEASE-p2)
CVE Name:       CVE-2014-3001

For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit <URL:http://security.FreeBSD.org/>.

I.   Background

The device file system, or devfs(5), provides access to kernel's device
namespace in the global file system namespace.

The devfs(5) rule subsystem provides a way for the administrator of a system
to control the attributes of DEVFS nodes.  Each DEVFS mount-point has a
``ruleset'', or a list of rules, associated with it, allowing the
administrator to change the properties, including the visibility, of certain

II.  Problem Description

The default devfs rulesets are not loaded on boot, even when jails are used.
Device nodes will be created in the jail with their normal default access
permissions, while most of them should be hidden and inaccessible.

III. Impact

Jailed processes can get access to restricted resources on the host system.
For jailed processes running with superuser privileges this implies access
to all devices on the system.  This level of access could lead to information
leakage and privilege escalation.

IV.  Workaround

Systems that do not run jails are not affected.

The system administrator can do the following to load the default ruleset:

/etc/rc.d/devfs onestart

Then apply the default ruleset for jails on a devfs mount using:

devfs -m ${devfs_mountpoint} rule -s 4 applyset

Or, alternatively, the following command will apply the ruleset over all devfs
mountpoints except the host one:

    mount -t devfs | grep -v '^devfs on /dev ' | awk '{print $3;}' | \
        xargs -n 1 -J % devfs -m % rule -s 4 applyset

After this, the system administrator should add the following configuration
to /etc/rc.conf to make it permanent, so the above operations do not have
to be done each time the host system reboots.


V.   Solution

Perform one of the following:

1) Upgrade your vulnerable system to a supported FreeBSD stable or
release / security branch (releng) dated after the correction date.

2) To update your vulnerable system via a source code patch:

The following patches have been verified to apply to the applicable
FreeBSD release branches.

a) Download the relevant patch from the location below, and verify the
detached PGP signature using your PGP utility.

# fetch http://security.FreeBSD.org/patches/SA-14:07/devfs.patch
# fetch http://security.FreeBSD.org/patches/SA-14:07/devfs.patch.asc
# gpg --verify devfs.patch.asc

b) Execute the following commands as root:

# cd /usr/src
# patch < /path/to/patch
# install -o root -g wheel -m 444 etc/defaults/rc.conf /etc/defaults/

Follow the steps described in the "Workaround" section, or reboot the

3) To update your vulnerable system via a binary patch:

Systems running a RELEASE version of FreeBSD on the i386 or amd64
platforms can be updated via the freebsd-update(8) utility:

# freebsd-update fetch
# freebsd-update install

VI.  Correction details

The following list contains the correction revision numbers for each
affected branch.

Branch/path                                                      Revision
- - -------------------------------------------------------------------------
stable/10/                                                        r265122
releng/10.0/                                                      r265124
- - -------------------------------------------------------------------------

To see which files were modified by a particular revision, run the
following command, replacing NNNNNN with the revision number, on a
machine with Subversion installed:

# svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base

Or visit the following URL, replacing NNNNNN with the revision number:


VII. References


The latest revision of this advisory is available at
Version: GnuPG v2.0.22 (FreeBSD)


- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:


Australian Computer Emergency Response Team
The University of Queensland
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
Comment: http://www.auscert.org.au/render.html?it=1967