CVE-2011-4930: Medium severity htcondor vulnerability
Multiple format string flaws were found in Condor:
a) when the XML message log format was requested in Condor submit job by remote Condor user and that user attempted to write a specially-crafted message into user log file via condorhold tool it could lead to condorschedd daemon crash, or, potentially arbitrary code execution with the privileges of the 'condor' user []. Also this way an attacker could potentially prevent other Condor jobs from being scheduled and ever executed,
b) request for file transfer by remote Condor user to transmit a file, with specially-crafted name, could lead to child process of condorschedd daemon to crash (repeated process, where condorschedd daemon would fork a child process to handle the request, the child to crash, while trying to handle it and condorschedd daemon to fork another child since the particular Condor job still have not been completed successfully).
Upstream bug report (mentioning only one attack vector): [1] https://condor-wiki.cs.wisc.edu/index.cgi/tktview?tn=2660
General upstream patch (addressing among these flaws also couple of compiler warning problems): [2] http://condor-git.cs.wisc.edu/?p=condor.git;a=commitdiff;h=5e5571d1a431eb3c61977b6dd6ec90186ef79867
-- [] Arbitrary code execution was possible only on systems, where Condor daemons were not compiled with FORTIFYSOURCE protection mechanism. On systems with this protection enabled, particular flaw would lead to Condor service crash only.
Other sources
Multiple format string vulnerabilities in Condor 7.2.0 through 7.6.4, and possibly certain 7.7.x versions, as used in Red Hat MRG Grid and possibly other products, allow local users to cause a denial of service (condorschedd daemon and failure to launch jobs) and possibly execute arbitrary code via format string specifiers in (1) the reason for a hold for a job that uses an XML user log, (2) the filename of a file to be transferred, and possibly other unspecified vectors.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2011-4930?
CVE-2011-4930 is classified as having a moderate severity level due to potential crashes of the condor_schedd daemon.
How do I fix CVE-2011-4930?
To fix CVE-2011-4930, upgrade Condor to version 7.6.0 or later, as the vulnerability has been addressed in these releases.
What versions of Condor are affected by CVE-2011-4930?
CVE-2011-4930 affects Condor versions 7.2.0 through 7.5.4.
What type of vulnerability is CVE-2011-4930?
CVE-2011-4930 is a format string vulnerability that could lead to crashes of the Condor scheduling daemon.
Who is impacted by CVE-2011-4930?
Users of the affected Condor versions, especially those executing jobs via the condor_hold tool, are impacted by CVE-2011-4930.