Condor upstream version 7.0.4 fixes following security issue (quoting upstream
This release fixes a problem causing possible incorrect handling of wild
cards in authorization lists. Examples of the configuration variables that
specify authorization lists are
If a configuration variable uses the asterisk character (*) in configuration
variables that specify the authorization policy, it is advisable to upgrade.
This is especially true for the use of wild cards in any DENY list, since
this problem could result in access being allowed, when it should have been
denied. This issue affects all previous versions of Condor.
CVE id CVE-2008-3424 was assigned to this issue:
Condor before 7.0.4 does not properly handle wildcards in the
ALLOW_WRITE, DENY_WRITE, HOSTALLOW_WRITE, or HOSTDENY_WRITE
configuration variables in authorization policy lists, which might
allow remote attackers to bypass intended access restrictions.
This issue only seems to affect configuration, when wild carded definition is used in DENY directive, and conflicting ALLOW authorization also exist. According to the documentation, such conflict should result in access being rejected, but this bug caused access to be allowed:
In most configurations, this problem can only be exploited by already authenticated user.
Verified fix on RHEL4 and RHEL5 with condor-7.0.4-4
condor-7.0.4-1.fc9 has been pushed to the Fedora 9 stable repository. If problems still persist, please make note of it in this bug report.
This issue was addressed in:
Red Hat Enterprise MRG for RHEL-4:
Red Hat Enterprise MRG for RHEL-5: