| Description: | Pacemaker is a high-availability cluster resource manager with a powerfulpolicy engine.A denial of service flaw was found in the way Pacemaker performedauthentication and processing of remote connections in certaincircumstances. When Pacemaker was configured to allow remote ClusterInformation Base (CIB) configuration or resource management, a remoteattacker could use this flaw to cause Pacemaker to block indefinitely(preventing it from serving other requests). (CVE-2013-0281)Note: The default Pacemaker configuration in Red Hat Enterprise Linux 6 hasthe remote CIB management functionality disabled.The pacemaker package has been upgraded to upstream version 1.1.10, whichprovides a number of bug fixes and enhancements over the previous version:* Pacemaker no longer assumes unknown cman nodes are safely stopped.* The core dump file now converts all exit codes into positive 'errno'values.* Pacemaker ensures a return to a stable state after too many fencingfailures, and initiates a shutdown if a node claimed to be fenced is stillactive.* The crm_error tool adds the ability to list and print error symbols.* The crm_resource command allows individual resources to be reprobed, andimplements the "--ban" option for moving resources away from nodes.The "--clear" option has replaced the "--unmove" option. Also, crm_resourcenow supports OCF tracing when using the "--force" option.* The IPC mechanism restores the ability for members of the haclient groupto connect to the cluster.* The Policy Engine daemon allows active nodes in the current membership tobe fenced without quorum.* Policy Engine now suppresses meaningless IDs when displaying anonymousclone status, supports maintenance mode for a single node, and correctlyhandles the recovered resources before they are operated on.* XML configuration files are now checked for non-printing characters andreplaced with their octal equivalent when exporting XML text. Also, a morereliable buffer allocation strategy has been implemented to preventlockups.(BZ#987355)Additional bug fixes:* The "crm_resource --move" command was designed for atomic resources andcould not handle resources on clones, masters, or slaves present onmultiple nodes. Consequently, crm_resource could not obtain enoughinformation to move a resource and did not perform any action. The "--ban"and "--clear" options have been added to allow the administrator toinstruct the cluster unambiguously. Clone, master, and slave resources cannow be navigated within the cluster as expected. (BZ#902407)* The hacluster user account did not have a user identification (UID) orgroup identification (GID) number reserved on the system. Thus, UID and GIDvalues were picked randomly during the installation process. The UID andGID number 189 was reserved for hacluster and is now used consistently forall installations. (BZ#908450)* Certain clusters used node host names that did not match the output ofthe "uname -n" command. Thus, the default node name used by the crm_standbyand crm_failcount commands was incorrect and caused the cluster to ignorethe update by the administrator. The crm_node command is now used insteadof the uname utility in helper scripts. As a result, the cluster behaves asexpected. (BZ#913093)* Due to incorrect return code handling, internal recovery logic of thecrm_mon utility was not executed when a configuration updated failed toapply, leading to an assertion failure. Return codes are now checkedcorrectly, and the recovery of an expected error state is now handledtransparently. (BZ#951371)* cman's automatic unfencing feature failed when combined with Pacemaker.Support for automated unfencing in Pacemaker has been added, and theunwanted behavior no longer occurs. (BZ#996850)All pacemaker users are advised to upgrade to these updated packages, whichcontain backported patches to correct these issues and add theseenhancements. |