RHEL 6 : rubygem-openshift-origin-node (RHSA-2014:0764)
Critical Nessus Plugin ID 119356
SynopsisThe remote Red Hat host is missing one or more security updates.
DescriptionAn updated rubygem-openshift-origin-node package that fixes one security issue and several bugs is now available for Red Hat OpenShift Enterprise 2.1.1.
The Red Hat Security Response Team has rated this update as having Critical security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section.
The rubygem-openshift-origin-node package provides basic OpenShift node functionality.
A command injection flaw was found in rubygem-openshift-origin-node. A remote, authenticated user permitted to install cartridges via the web interface could use this flaw to execute arbitrary code with root privileges on the Red Hat OpenShift Enterprise node server.
This issue was discovered by Jeremy Choi of the Red Hat HSS Pen-test Team.
The rubygem-openshift-origin-node package has been upgraded to version 18.104.22.168. Additionally, the rubygem-openshift-origin-container-selinux package has been upgraded to version 0.8.1.2, as needed by the updated rubygem-openshift-origin-node package.
This update also fixes the following bugs :
* The syslog_logger.rb implementation on nodes made incorrect use of the Ruby Syslog library. Raw log message input was handled as a Syslog format string, causing failures for many application operations. This bug fix updates the implementation to correctly handle raw log message input, and the failures no longer occur. (BZ#1096900)
* Under certain conditions, it was possible for the MCollective agent on nodes to fail to fully initialize while checking the status of a cartridge. This resulted in sporadic failures of rhc cartridge status.
This bug fix ensures that the agent is always fully initialized.
* Developers encountered syntax errors when connecting to a gear using the 'rhc ssh' command if the gear was hosted on a node with quotas disabled. This was due to the command trying to report quota information but being given an empty string because quotas were disabled. This bug fix updates the handling for reporting on quotas when there is no information to report, and the syntax errors no longer occur. (BZ#1107801)
* If a file containing invalid special characters was placed in an application's ~/.env/user_vars directory, subsequent interactions with the application using SSH or Git were refused. This was due to problems with the node component handling the invalid characters. This bug fix updates the node component to handle problematic files in ~/.env/user_vars; as a result, interactions with the application using SSH or Git succeed as normal. (BZ#1096833)
All rubygem-openshift-origin-node users are advised to upgrade to this updated package, which contains a backported patch to correct this issue.
SolutionUpdate the affected rubygem-openshift-origin-container-selinux and / or rubygem-openshift-origin-node packages.