Red Hat OpenShift Enterprise before 2.2 does not properly restrict access to gears, which allows remote attackers to access the network resources of arbitrary gears via unspecified vectors.

The remote Redhat Enterprise Linux 6 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2014:1796 advisory.

    OpenShift Enterprise by Red Hat is the company's cloud computing     Platform-as-a-Service (PaaS) solution designed for on-premise or private     cloud deployments.

    It was reported that OpenShift Enterprise 2.2 did not properly restrict     access to services running on different gears. This could allow an attacker     to access unprotected network resources running in another user's gear.
    OpenShift Enterprise 2.2 introduces the oo-gear-firewall command which     creates firewall rules and SELinux policy to contain services running on     gears to their own internal gear IPs. The command is invoked by default     during new installations of OpenShift Enterprise 2.2 to prevent this     security issue. Administrators should run the following on node hosts in     existing deployments after upgrading to 2.2 to address this security issue:

    # oo-gear-firewall -i enable -s enable

    Please see the man page for the oo-gear-firewall command for more details.
    (CVE-2014-3674)

    It was reported that OpenShift Enterprise did not restrict access to the     /proc/net/tcp file on gears, which allowed local users to view all     listening connections and connected sockets. This could result in remote     systems IP or port numbers in use being exposed which may be useful for     further targeted attacks. Note that for local listeners, OSE restricts     connections to within the gear by default, so even with the knowledge of     the local port and IP the attacker is unable to connect. This bug fix     updates the SELinux policy on node hosts to prevent this gear     information from being accessed by local users. (CVE-2014-3602)

    The OpenShift Enterprise 2.2 Release Notes provide information about new     features and notable technical changes in this release, as well as notes on     initial installations. For more information about OpenShift Enterprise, see     the documentation available at:

    https://access.redhat.com/site/documentation/en-US/OpenShift_Enterprise/2/

    All OpenShift Enterprise users are advised to upgrade to release 2.2.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise Linux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Red Hat OpenShift Enterprise release 2.1.9, which fixes two security issues, several bugs, and add one enhancement, is now available.

Red Hat Product Security has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section.

OpenShift Enterprise by Red Hat is the company's cloud computing Platform-as-a-Service (PaaS) solution designed for on-premise or private cloud deployments.

It was found that OpenShift Enterprise 2.1 did not properly restrict access to services running on different gears. This could allow an attacker to access unprotected network resources running in another user's gear.

In a previous update, OpenShift Enterprise 2.2 introduced the oo-gear-firewall command, which creates firewall rules and SELinux policy to contain services running on gears to their own internal gear IPs. The command is invoked by default during new installations of OpenShift Enterprise 2.2 to prevent this security issue. This update backports the command to OpenShift Enterprise 2.1.; administrators should run the following command on node hosts in existing OpenShift Enterprise 2.1 deployments after applying this update to address this security issue :

# oo-gear-firewall -i enable -s enable

Please see the man page of the oo-gear-firewall command for more details. (CVE-2014-3674)

It was found that OpenShift Enterprise did not restrict access to the /proc/net/tcp file in gears, which allowed local users to view all listening connections and connected sockets. This could result in remote system's IP or port numbers in use to be exposed, which may be useful for further targeted attacks.

Note that for local listeners, OpenShift Enterprise restricts connections to within the gear by default, so even with the knowledge of the local port and IP, the attacker is unable to connect. The SELinux policy on node hosts has been updated to prevent this gear information from being accessed by local users.

Due to the closing of this access, JBoss-based cartridges that relied on it previously must be upgraded according to the standard procedure.
This is a compatible cartridge upgrade and therefore does not require a restart. (CVE-2014-3602)

Space precludes documenting all of the bug fixes and enhancements in this advisory. See the OpenShift Enterprise Technical Notes linked to in the References section, which will be updated shortly for release 2.1.9, for details about these changes.

All OpenShift Enterprise users are advised to upgrade to these updated packages.

ID	Name	Product	Family	Severity
119441	RHEL 6 : Red Hat OpenShift Enterprise 2.2 Release Advisory (Moderate) (RHSA-2014:1796)	Nessus	Red Hat Local Security Checks	high
119357	RHEL 6 : Red Hat OpenShift Enterprise 2.1.9 (RHSA-2014:1906)	Nessus	Red Hat Local Security Checks	high

Detections

Analytics

CVE-2014-3674

high

Tenable Plugins

high

high