RedHat: Moderate: condor security and bug fix update
Summary
Condor is a specialized workload management system for compute-intensive
jobs. It provides a job queuing mechanism, scheduling policy, priority
scheme, and resource monitoring and management.
A flaw was found in the way Condor interpreted wildcards in authorization
lists. Certain authorization lists using wildcards in DENY rules, such as
DENY_WRITE or HOSTDENY_WRITE, that conflict with the definitions in ALLOW
rules, could permit authenticated remote users to submit computation jobs,
even when such access should have been denied. (CVE-2008-3424)
Bug fixes:
* the /etc/condor/condor_config file started with "What machine is your
central manager?". The following line was blank, instead of having the
"CONDOR_HOST" option, causing confusion. The "What machine..." text is now
removed.
* condor_config.local defined "LOCK = /tmp/[lock file]". This is no longer
explicitly defined; however, lock files may be in "/tmp/", and could be
removed by tmpwatch. A "LOCK_FILE_UPDATE_INTERVAL" option, which defaults
to eight hours, has been added. This updates the timestamps on lock files,
preventing them from being removed by tools such as tmpwatch.
* when a "SCHEDD_NAME" name in condor_config ended with an "@", the
system's hostname was appended. For example, if "SCHEDD_NAME = test@" was
configured, "condor_q -name test@" failed with an "Collector has no record
of schedd/submitter" error. Now, the hostname is not appended when a name
ends with an "@". In High Availability (HA) Schedd deployments, this allows
a name to be shared by multiple Schedds.
* when too few arguments were passed to "condor_qedit", such as
"condor_qedit -constraint TRUE", a segfault occurred. Better argument
handling has been added to resolve this.
* due to missing common_createddl.sql and pgsql_createddl.sql files,
it was not possible to use Quill. Now, these files are included in
"/usr/share/condor/sql/".
* "condor_submit -dump ad [file-name]" caused a segfault if the [file-name]
job contained "universe = grid".
* previously, a condor user and group were created if they did not exist,
without specifying a specific UID and GID. Now, UID and GID 64 are used.
The effect of this change is non-existent if upgrading the condor packages.
If an existing condor user and group are manually changed, problems with
file ownership will occur.
Configuration changes (from the Condor release notes - see link below):
* a new CKPT_SERVER_CHECK_PARENT_INTERVAL variable sets the time interval
between a checkpoint server checking if its parent is running. If the
parent server has died, the checkpoint server is shut down.
* a new CKPT_PROBE variable to define an executable for the helper process
Condor uses for information about the CheckpointPlatform attribute.
* STARTER_UPLOAD_TIMEOUT now defaults to 300 seconds.
* new variables (booleans) PREEMPTION_REQUIREMENTS_STABLE and
PREEMPTION_RANK_STABLE, configure whether attributes used in
PREEMPTION_REQUIREMENTS and PREEMPTION_RANK change during negotiation
cycles.
* a new GRIDMANAGER_MAX_WS_DESTROYS_PER_RESOURCE variable, with a
default value of 5, defines the number of simultaneous WS destroy commands
that can be sent to a server for type gt4 grid universe jobs.
* now, VALID_SPOOL_FILES automatically includes the "SCHEDD.lock" lock file
for condor_schedd HA failover.
* the default value for SEC_DEFAULT_SESSION_DURATION has been changed from
8640000 seconds (100 days) to 86400 seconds (one day).
Important: these updated packages upgrade Condor to version 7.0.4. For a
full list of changes, refer to the Condor release notes:
condor users should upgrade to these updated packages, which resolve these
issues.
Summary
Solution
Before applying this update, make sure that all previously-released
errata relevant to your system have been applied.
This update is available via Red Hat Network. Details on how to use
the Red Hat Network to apply this update are available at
References
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-3424 http://www.redhat.com/security/updates/classification/#moderate
Package List
Red Hat MRG Grid for RHEL-4 AS:
Source:
i386:
condor-7.0.4-4.el4.i386.rpm
condor-debuginfo-7.0.4-4.el4.i386.rpm
condor-static-7.0.4-4.el4.i386.rpm
condor-test-7.0.4-4.el4.i386.rpm
x86_64:
condor-7.0.4-4.el4.x86_64.rpm
condor-debuginfo-7.0.4-4.el4.x86_64.rpm
condor-static-7.0.4-4.el4.x86_64.rpm
condor-test-7.0.4-4.el4.x86_64.rpm
Red Hat MRG Grid for RHEL-4 ES:
Source:
i386:
condor-7.0.4-4.el4.i386.rpm
condor-debuginfo-7.0.4-4.el4.i386.rpm
condor-static-7.0.4-4.el4.i386.rpm
condor-test-7.0.4-4.el4.i386.rpm
x86_64:
condor-7.0.4-4.el4.x86_64.rpm
condor-debuginfo-7.0.4-4.el4.x86_64.rpm
condor-static-7.0.4-4.el4.x86_64.rpm
condor-test-7.0.4-4.el4.x86_64.rpm
These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from
https://www.redhat.com/security/team/key/#package
Topic
Updated condor packages that fix a security issue and several bugs are now available for Red Hat Enterprise MRG.
This update has been rated as having moderate security impact by the Red Hat Security Response Team.
Topic
Relevant Releases Architectures
Red Hat MRG Grid for RHEL-4 AS - i386, x86_64
Red Hat MRG Grid for RHEL-4 ES - i386, x86_64
Bugs Fixed
457265 - Rebase on Condor 7.0.4
457266 - condor_submit -dump segfaults when universe = grid
457267 - Red Hat RPMs should identify their buildid, differentiate from UW's builds
457268 - Necessary Quill setup files?
457269 - condor_qedit segfault with too few arguments
457270 - SCHEDD_NAME always appends @$(FULL_HOSTNAME)
457271 - condor_config.local sets up LOCK in /tmp
457272 - /etc/condor/condor_config file missing CONDOR_HOST = option
457372 - CVE-2008-3424 condor: incorrect handling of wild cards in authorization lists
458069 - Add newly assigned UID/GID for condor to product
